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 transilienceai/communitytools --skill pci-secure-softwaregit clone --depth 1 https://github.com/transilienceai/communitytoolsWrote 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/transilienceai/communitytools/pci-secure-software)<a href="https://agentmods.dev/skills/transilienceai/communitytools/pci-secure-software"><img src="https://agentmods.dev/badge/skills/transilienceai/communitytools/pci-secure-software/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/transilienceai/communitytools/pci-secure-software"><img src="https://agentmods.dev/badge/skills/transilienceai/communitytools/pci-secure-software.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00162 | $0.01696 |
| Opus 5 | $0.00081 | $0.00848 |
| Sonnet 5 | $0.00032 | $0.00339 |
| Haiku 4.5 | $0.00016 | $0.00170 |
Grade A, and why
pci-secure-software 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 9d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pci-secure-software
About this skill
A knowledge layer + orchestration contract for running a forensically-defensible PCI Secure Software Standard (SSS) v2.0 readiness assessment of an application end-to-end, from its source code, design documentation, and dependency manifests. Every verdict is anchored to a real file:line + quoted snippet; every requirement comes from a pinned catalog, never model memory.
This is a readiness gap-analysis, not an official PCI validation. The PCI SSS defines no In-Place/Not-in-Place marking scheme — marking occurs solely in the ROV/AOV templates assessed by a qualified assessor. Say so in every report.
Persona — Asa
When you operate this tool you are Asa, a senior software-security assessor. Methodical, catalog-grounded, honest about scope. Walk the pipeline cleanly; one status line per phase. When evidence cannot prove a requirement, you record REQUIRES_MANUAL_REVIEW — never a convenient MET. You fail closed.
What you produce
Per applicable Test Requirement: a status verdict + the evidence that proves it (or the gap) + the why + a remediation suggestion. Aggregated into Compliance-Assessment-Report.pdf + compliance-report.json + tracker.csv, gated on 100% coverage and deterministic citation verification.
The deterministic source of truth
The requirement set is never generated by the model. It is loaded from the pinned catalog reference/catalog/pci-sss-v2.0.json (one entry per lettered Test Requirement) and filtered to the applicable set by tools/pci-sss/applicability.py. See reference/catalog/INDEX.md and reference/core/applicability.md.
6-phase pipeline
- INTAKE — scaffold the engagement OUTPUT_DIR; parse the scope file; fingerprint the tech stack (
skills/techstack-identification); capture the 7-keyAppContext. - APPLICABILITY — evidence-backed APPLICABLE/NOT_APPLICABLE per conditional Security Objective (4, 7) and Module (A/B/C/D); excluding any unit requires negative evidence. Build the deterministic work-list. See
reference/core/applicability.md. - GATHER — per objective family, gather source/doc evidence using the matching
reference/scenarios/playbook and reused sub-skills. - DYNAMIC — where a requirement needs dynamic analysis and a running instance is authorized, perform it (incl. negative testing); otherwise the requirement is
REQUIRES_MANUAL_REVIEW, never a fakedMET. - VERDICT + VERIFY — assign each Test Requirement a status with cited evidence; N blind adversarial refuters attack every MET;
tools/pci-sss/citation_verify.pygreps every citation; quarantine + downgrade on miss; aggregate letter verdicts → requirement → objective. - REPORT — coverage-gated gap report with the disclaimer + a Coverage & Limitations section listing every manual-review / quarantined / dynamic-not-run item.
What ships with it
25 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.
- reference/agents/citation-verifier.md 2.2 KB
- reference/agents/dynamic-tester.md 2.6 KB
- reference/agents/evidence-gatherer.md 2.4 KB
- reference/agents/refutation-validator.md 2.5 KB
- reference/agents/verdict-assessor.md 2.9 KB
- reference/anti-hallucination/citation-verifier.md 2.8 KB
- reference/anti-hallucination/control-stack.md 3.6 KB
- reference/anti-hallucination/coverage-gate.md 2.8 KB
- reference/catalog/INDEX.md 4.2 KB
- reference/catalog/pci-sss-v2.0.json 377 KB
- reference/core/applicability.md 4.9 KB
- reference/core/schema.md 8.8 KB
- reference/INDEX.md 3.2 KB
- reference/reporting/gap-report.md 4.5 KB
- reference/reporting/output-discipline.md 2.6 KB
- reference/scenarios/architecture-composition.md 7.8 KB
- reference/scenarios/crypto-key-management.md 9.9 KB
- reference/scenarios/module-a-account-data.md 6.9 KB
- reference/scenarios/module-b-poi.md 7.8 KB
- reference/scenarios/module-c-web.md 8.9 KB
- reference/scenarios/module-d-sdk.md 8.3 KB
- reference/scenarios/protection-and-modes.md 9.9 KB
- reference/scenarios/sensitive-assets.md 10 KB
- reference/scenarios/threats-and-deployment.md 9.5 KB
- reference/VERSIONS.md 2.1 KB
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.
- 9d ago First seen · 84 lines · 162 tokens per session scan A 9686341978e1
pci-secure-software is a skill published in the GitHub repository transilienceai/communitytools (515 stars, last pushed 1mo ago), licensed MIT. It adds 162 tokens to every session and 1,696 once invoked, about $0.0008 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.
Other skills, from other repositories
Web Application Security Testing
OWASP Top 10 testing, injection vulnerability detection, API security assessment, authentication testing, and web vulnerability reporting for authorized assessments.
identity-auth
Test identity, authentication, authorization, and sessions.
business-logic
Test workflows, state transitions, pricing, and concurrency.
command-execution
Security-focused command execution techniques for penetration testing. Use this skill when executing system commands during authorized security assessments. Covers Windows and Linux command execution, common security testing commands, and best practices for avoiding detection.
pentest-validation
Orchestrate security finding validation through graduated exploitation. 4-phase pipeline: recon (SAST/DAST), analysis (code review), validation (exploit proof), report (No Exploit, No Report gate). Eliminates false positives by proving exploitability.
reverse-skill
Reverse-skill directs AI coding agents to the right methodology for reverse engineering, authorized penetration testing, and related security research tasks. The README describes 44 documented routing paths across tracked security disciplines, along with automation scripts and a CTF sandbox orchestrator for evidence…