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 fastrevmd-lab/fwskillsshare --skill pci-ngfw-compliancegit clone --depth 1 https://github.com/fastrevmd-lab/fwskillsshareWrote 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/fastrevmd-lab/fwskillsshare/pci-ngfw-compliance)<a href="https://agentmods.dev/skills/fastrevmd-lab/fwskillsshare/pci-ngfw-compliance"><img src="https://agentmods.dev/badge/skills/fastrevmd-lab/fwskillsshare/pci-ngfw-compliance/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/fastrevmd-lab/fwskillsshare/pci-ngfw-compliance"><img src="https://agentmods.dev/badge/skills/fastrevmd-lab/fwskillsshare/pci-ngfw-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.03244 |
| Opus 5 | $0.00041 | $0.01622 |
| Sonnet 5 | $0.00016 | $0.00649 |
| Haiku 4.5 | $0.00008 | $0.00324 |
Grade A, and why
pci-ngfw-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 11d 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.
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 NGFW Compliance Research
Overview
Use this skill to answer questions like “what does an NGFW need to do to be PCI compliant?” or “is this firewall design sufficient for PCI DSS?” The core answer is: a next-generation firewall is not PCI compliant by itself. PCI DSS compliance is assessed for the entity, the cardholder data environment (CDE), connected-to/security-impacting systems, processes, people, evidence, and compensating or customized controls. An NGFW can be a major network security control (NSC), but it must be configured, maintained, monitored, reviewed, and evidenced as part of the whole PCI DSS program.
For PCI DSS v4.0.1, the most directly relevant NGFW areas are Requirement 1 (Install and Maintain Network Security Controls), Requirement 2 (secure configuration of system components), Requirement 4 (strong cryptography over open/public networks), Requirement 6.4.2 (automated technical solution for public-facing web applications), Requirement 8 (unique IDs, authentication, and MFA for administrative, remote, and CDE access), Requirement 10 (logging and monitoring), Requirement 11 (vulnerability scanning, penetration testing, segmentation testing, IDS/IPS), and Requirement 12 (policies, risk, incident response, and operational governance).
Treat this as research and assessment guidance, not legal advice and not a QSA decision. When producing final compliance language, cite PCI DSS v4.0.1 requirement IDs and defer final interpretation to the entity’s QSA/ISA, acquirer, or payment brand.
Runtime intake
Before starting the workflow, inspect the request, supplied artifacts, and
available approved read-only evidence. If unresolved facts could materially
change safety, scope, correctness, confidence, or the requested output, read
references/runtime-intake.md.
For each unresolved material fact whose catalog condition is true, invoke Claude AskUserQuestion or Codex request_user_input before continuing or issuing an open-ended request.
Ask at most three single-select catalog questions per round. After each response, ask another round whenever any unresolved material catalog condition remains true; continue only when none remain. Do not repeat answered questions or show the full catalog.
Without a native tool, present each selected catalog question with its 2-3 labeled choices and a free-text Other path in concise plain text; do not substitute a generic checklist.
What ships with it
4 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.
- 11d ago First seen · 213 lines · 81 tokens per session scan A ce5323ce18d7
pci-ngfw-compliance is a skill published in the GitHub repository fastrevmd-lab/fwskillsshare (8 stars, last pushed 14d ago), licensed MIT. It adds 81 tokens to every session and 3,244 once invoked, about $0.0004 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-31.
Other skills, from other repositories
fmc-firewall-ops
Cisco Secure Firewall FMC — access policy search, rule inspection, FTD device targeting, multi-FMC profile management. Use when searching firewall rules by IP or FQDN, checking if host A can reach host B through the firewall, auditing FMC access policies, or reviewing SGT-based segmentation rules.
fortianalyzer-ops
FortiAnalyzer log operations — policy-filtered traffic log query within a bounded time window, offset pagination, per-policy activity checks, and logging-device inventory. Use when asking whether traffic actually matched a firewall rule, investigating what hit a policy, or determining whether a rule is genuinely…
fortigate-ops
FortiGate device operations — system status, interfaces, routing, IPsec VPN tunnel state with phase 1 and phase 2 reported separately, HA member identification, per-VDOM scoping, and manager-vs-device drift detection. Use when asking what a FortiGate is ACTUALLY doing right now, whether a tunnel is up, or whether the…
fortimanager-ops
FortiManager policy operations — ADOM inventory, policy package review, recursive object resolution, revision history, install preview, and gated package install. Use when auditing FortiGate firewall policy at the MANAGER level (intent), reviewing ADOM policy packages, or planning a package install with rollback…
meraki-security-appliance
Cisco Meraki MX security appliance (read-only) — L3/L7 firewall rules, content filtering, IDS/IPS and AMP settings, site-to-site VPN, traffic shaping via Cisco's official Meraki MCP. Use when auditing Meraki firewall rules, reviewing content filtering, or inspecting MX VPN configuration.
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.