pci-audit

pci-audit is a skill for Claude Code from briiirussell/cybersecurity-skills. It costs 180 tokens per session (3,453 once invoked), scanned A, original, MIT.

An engineering audit guide for environments that store, process, or transmit payment card data. It uses PCI DSS v4.0, the security standard for those environments, with special attention to deciding which systems are in scope.

In plain words
What is it for?
Use it to assess card-data storage and transmission, secure software development, access, logging, testing, incident response, and preparation for a self-assessment or qualified security assessor review.
Why use it?
It helps prevent teams from overlooking connected systems that can affect card-data security. Establishing scope first clarifies which security, access, logging, development, and response requirements apply.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the cybersecurity-skills plugin — 28 skills shipped together

Good fit Use it to assess card-data storage and transmission, secure software development, access, logging, testing, incident response, and preparation for a self-assessment or qualified security assessor review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/briiirussell/cybersecurity-skills/pci-audit
Install

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.

Any agent
npx skills add briiirussell/cybersecurity-skills --skill pci-audit
Clone the repo
git clone --depth 1 https://github.com/briiirussell/cybersecurity-skills

Made for: Claude Code.

Or install cybersecurity-skills, the plugin that ships this one along with the rest of its 28 skills.

Wrote 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.

agentmods badge for pci-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/briiirussell/cybersecurity-skills/pci-audit/github.svg)](https://agentmods.dev/skills/briiirussell/cybersecurity-skills/pci-audit)
Your own site
<a href="https://agentmods.dev/skills/briiirussell/cybersecurity-skills/pci-audit"><img src="https://agentmods.dev/badge/skills/briiirussell/cybersecurity-skills/pci-audit/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.

agentmods 80×15 button for pci-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/briiirussell/cybersecurity-skills/pci-audit"><img src="https://agentmods.dev/badge/skills/briiirussell/cybersecurity-skills/pci-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 180 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,453 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00180 $0.03453
Opus 5 $0.00090 $0.01726
Sonnet 5 $0.00036 $0.00691
Haiku 4.5 $0.00018 $0.00345

Measured 13d ago against content hash defd12a55c8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pci-audit 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 13d 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.

skills/pci-audit/SKILL.md · 213 lines

How it starts

The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PCI Audit — Payment Card Industry Data Security Standard

PCI DSS v4.0 (effective March 2025) is the security standard for any environment that stores, processes, or transmits payment card data. Twelve high-level requirements; hundreds of sub-requirements. Most organizations pass or fail on a single decision: scope.

This skill emphasizes scope determination first, then the engineering-relevant requirements. Final compliance attestation (SAQ self-assessment or QSA audit producing an Attestation of Compliance) is a process this skill prepares for — it is not the attestation itself.

Cross-references: crypto-audit for Req 3 / 4 cryptographic detail; iam-audit for Req 7-8; siem-detection for Req 10 logging; dependency-audit and owasp-audit for Req 6 (secure SDLC); incident-triage for Req 12.10 (incident response).

The scope question (do this first)

"Scope" in PCI DSS means: the systems that store, process, or transmit cardholder data (CHD), plus systems that can affect the security of those systems (connected-to and security-impacting systems). Everything in scope is subject to all 12 requirements. Everything out of scope is not.

Most PCI failures are scope failures. A system pulled into scope by accident creates years of compliance debt; a system kept out of scope via good architecture saves substantial cost.

Determine scope

For every system in the environment, classify:

Type Definition In scope?
CDE (Cardholder Data Environment) Stores, processes, or transmits PAN, expiration, service code, name when paired with PAN, or sensitive authentication data Yes — full PCI DSS
Connected-to Has direct connectivity to the CDE without compensating segmentation Yes
Security-impacting Provides security services to the CDE (auth, logging, monitoring, time sync, DNS) Yes
Segmented No direct connectivity; segmentation validated annually No
Cardholder data flow only as masked / tokenized The system handles tokens or masked PANs that cannot be reversed without out-of-band access Usually No, but verify the token type — surrogate tokens reversible by the merchant are still in scope

Read the full file on GitHub · 213 lines

Changes

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.

  1. 13d ago First seen · 213 lines · 180 tokens per session scan A defd12a55c8a

Subscribe to this mod's changes

pci-audit is a skill published in the GitHub repository briiirussell/cybersecurity-skills (391 stars, last pushed 3mo ago), licensed MIT. It adds 180 tokens to every session and 3,453 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

specification-writing

A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

x-scorecard

OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 57 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens