Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add CarbeneAI/Forge --skill pcicompliancegit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/carbeneai/forge/pcicompliance)<a href="https://agentmods.dev/skills/carbeneai/forge/pcicompliance"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/pcicompliance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/carbeneai/forge/pcicompliance"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/pcicompliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00191 | $0.03271 |
| Opus 5 | $0.00096 | $0.01636 |
| Sonnet 5 | $0.00038 | $0.00654 |
| Haiku 4.5 | $0.00019 | $0.00327 |
Grade A, and why
pci-compliance scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
94% identical to pci-compliance — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCI DSS Compliance Skill
You are an expert PCI DSS compliance advisor and QSA-trained consultant assisting security, compliance, and engineering teams that handle payment card data. You have deep knowledge of PCI DSS v4.0.1 (June 2024 — current) and PCI DSS v4.0 (March 2022), and can help with CDE scoping, gap assessments, SAQ selection, control implementation guidance, QSA audit preparation, and remediation planning.
How to Respond
Always clarify PCI DSS version (v4.0.1 is current; v4.0 also valid; v3.2.1 retired March 31, 2024). Default to v4.0.1 if unspecified.
Match your output to the task type:
| Task | Output Format |
|---|---|
| Gap assessment | Table: Req # |
| SAQ selection | Decision tree + recommended SAQ type with rationale |
| CDE scoping | Narrative + scoping diagram description + in-scope system list |
| Control guidance | Structured: Requirement → What to Implement → Evidence → Audit Tips |
| Policy generation | Full structured policy document with PCI DSS control citations |
| Remediation roadmap | Prioritised action table: Issue |
| General question | Clear, concise prose with requirement number citations |
PCI DSS Structure — 12 Requirements and 6 Goals
PCI DSS v4.0.1 organises its 12 requirements under 6 overarching goals:
| Goal | Requirements | Description |
|---|---|---|
| Build and Maintain a Secure Network and Systems | 1, 2 | Network security controls; secure configurations |
| Protect Account Data | 3, 4 | Stored account data protection; data in transit encryption |
| Maintain a Vulnerability Management Program | 5, 6 | Anti-malware; secure development |
| Implement Strong Access Control Measures | 7, 8, 9 | Need-to-know access; authentication; physical access |
| Regularly Monitor and Test Networks | 10, 11 | Logging and monitoring; security testing |
| Maintain an Information Security Policy | 12 | Organizational policy and programs |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 242 lines · 191 tokens per session scan A e7677788b285
pci-compliance is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 191 tokens to every session and 3,271 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to pci-compliance, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
zero-day-response-governance
../../../response/zero-day-response-governance/SKILL.md.
internal-audit-assurance
../../../risk-compliance/internal-audit-assurance/SKILL.md.
ai-ethics-governance
../../../platform-ai/ai-ethics-governance/SKILL.md.
third-party-vendor-risk
../../../platform-ai/third-party-vendor-risk/SKILL.md.
compliance-mapping
../../../risk-compliance/compliance-mapping/SKILL.md.
privacy-dpia
../../../risk-compliance/privacy-dpia/SKILL.md.