Map code changes to PCI-DSS and MAS TRM compliance controls
FSI Compliance Checker maps a proposed change against PCI-DSS v4.0 and MAS TRM controls using domain-organized reference files.
18.13.0Add to Favorites
Why it matters
Ensure financial services code changes meet regulatory compliance requirements by automatically mapping modifications to PCI-DSS v4.0 and MAS Technology Risk Management controls, surfacing which regulations apply to each change.
Outcomes
What it gets done
Review code diffs and identify which PCI-DSS v4.0 requirements are triggered
Map architectural changes to MAS TRM control domains
Surface compliance gaps before code reaches production
Generate structured compliance reports with specific control references
Install
Add it to your toolbox
Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-fsi-compliance-checker | bash After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.
Reports
Agent outcome reports
No reports yet
Overview
FSI Compliance Checker is an instruction-only Kiro and Claude Code skill that maps a proposed change to PCI-DSS v4.0 and MAS TRM compliance controls, backed by domain-organized reference files. It ships as part of a larger open-source Agent Skills collection alongside Secure SDLC and Cloud Architecture review skills. Use it when a change in a financial-services context needs checking against PCI-DSS v4.0 or MAS TRM controls before it ships.
What it does
FSI Compliance Checker is one of the skills in the "Agentic Skills Best Practices" collection, built for AWS solutions architects and developers using Kiro, and does exactly what the repository describes it for: it maps a proposed code or infrastructure change to PCI-DSS v4.0 and MAS (Monetary Authority of Singapore) Technology Risk Management (TRM) controls, backed by domain-organized reference files rather than one flat rulebook. Like the collection's other instruction-only skills - the Secure SDLC role skills and the Cloud Architecture Well-Architected review skill - it needs nothing from the host beyond support for the Agent Skills specification. It is plain markdown with no bundled executable scripts, so it does not require a platform that permits code execution.
When to use - and when NOT to
Use it when a change needs to be checked against PCI-DSS v4.0 or MAS TRM compliance controls before it ships - the kind of review an AWS SA or developer working in a financial-services context would otherwise do by hand against two separate regulatory frameworks. It is not one of the repository's three flagship, evidence-backed skills (agentcore-harness-builder, gitlab-ci-kiro-pipeline, ai-native-sdlc), which are validated end-to-end against real AWS infrastructure or ship their own enforcement gate with mutation-proven tests and signed releases - FSI Compliance Checker is an instruction-only reference skill without that level of documented external verification. It is also not a document-generation skill (docx, pdf, pptx, xlsx); the repository deliberately excludes those and points to Anthropic's own anthropics/skills repository for them instead.
Inputs and outputs
As an instruction-only skill it is plain markdown plus domain-organized reference files for its PCI-DSS v4.0 and MAS TRM controls, and needs nothing beyond a host that implements the Agent Skills specification's standard fields (name, description, license, metadata) - no platform-private extensions, no bundled scripts, and no extra runtime dependencies to install.
Integrations
Install it like any skill in this repository: ./install.sh <skill-name>, or ./install.sh --all for the whole collection, into ~/.kiro/skills/ (global) or .kiro/skills/ (project) for Kiro, or ~/.claude/skills/ (or via the plugin marketplace) for Claude Code. The repository's skills are portable by construction across every platform that implements the Agent Skills specification - Kiro IDE and CLI, Claude Code, Claude.ai, and the Claude API - and this repository's skills have been verified end-to-end on both Kiro and Claude Code, per its own TESTING.md. Every push and pull request is checked by a GitHub Actions workflow that validates SKILL.md frontmatter, required fields, and naming conventions.
Who it's for
AWS solutions architects and developers working in or adjacent to financial services who want a repeatable, reference-file-backed way to map a change against PCI-DSS v4.0 and MAS TRM controls, alongside the same collection's broader Secure SDLC and Cloud Architecture review skills. It is licensed under the MIT License, along with the rest of the repository's own docs, workshop material, and engineering skills - a handful of example skills imported from Anthropic's own repository are separately licensed Apache 2.0.
Source README
Maps a concrete change (code diff, architecture design, IaC, pipeline config) to the specific controls it touches in financial services compliance frameworks - PCI-DSS v4.0.1 for payment card data and MAS TRM for Singapore-regulated institutions - and reports gaps with actionable remediation. This is engineering-level compliance triage: it helps teams catch violations before audit, but it does not replace a qualified assessor (QSA) or the institution's compliance function. Say so in every report.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.