Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmnpx agentmods add skills/dungnotnull/hybrid-harness-chaos-process-prm/s30-compliance-auditWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s30-compliance-audit)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s30-compliance-audit"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s30-compliance-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.
<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s30-compliance-audit"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s30-compliance-audit.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.00114 | $0.04825 |
| Opus 5 | $0.00057 | $0.02413 |
| Sonnet 5 | $0.00023 | $0.00965 |
| Haiku 4.5 | $0.00011 | $0.00483 |
Grade A, and why
compliance-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 12d 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 — 545 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance & Audit (s30)
Purpose
Automate the collection, organization, and presentation of compliance evidence across the entire SDLC — proving to auditors, regulators, and stakeholders that security controls, change management, access controls, and resilience testing are implemented, tested, and continuously verified.
Prerequisites
- All security scan evidence from s11
- Observability logs from s22
- Resilience scores from s26
- Release management records from s28
- Disaster recovery plan from s29 (if available)
- Applicable compliance framework requirements identified
Input Contract
| Input | Source | Required |
|---|---|---|
| Security scan history | s11 output (all runs) | Yes |
| Policy governance rules + violations | s22 output | Yes |
| Access control / RBAC configuration | s06 (delegate RBAC), s22 | Yes |
| Release history with approvals | s28 output | Yes |
| Change management records | s28 (go/no-go decisions) | Yes |
| DR test results | s29 output | Yes |
| Resilience scores | s26 output | Yes |
| Compliance framework requirements | s01 (PRD — compliance section) | Yes |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Compliance evidence package | .commandcode/artifacts/compliance/evidence-<framework>-<date>.json |
JSON |
| Audit trail report | .commandcode/artifacts/compliance/audit-trail-<period>.md |
Markdown |
| Control mapping matrix | .commandcode/artifacts/compliance/control-mapping.yaml |
YAML |
| Compliance dashboard | .commandcode/artifacts/compliance/dashboard.json |
JSON (Grafana) |
| Gap analysis report | s01 (re-analysis), s25 (postmortem) | Markdown |
| Auditor-ready evidence bundle | .commandcode/artifacts/compliance/auditor-bundle-<date>.zip |
ZIP archive |
Compliance Framework Coverage
supported_frameworks:
SOC2:
trust_criteria:
- Security
- Availability
- Confidentiality
evidence_sources:
- Access logs (who deployed what, when)
- Change approval records
- Security scan history
- Incident response records
HIPAA:
rules:
- Privacy Rule
- Security Rule
- Breach Notification Rule
evidence_sources:
- PHI access audit logs
- Encryption-at-rest verification
- Encryption-in-transit verification
- Access control reviews
GDPR:
principles:
- Data minimization
- Purpose limitation
- Storage limitation
- Integrity and confidentiality
evidence_sources:
- Data retention policies
- Right-to-erasure capability proof
- Data processing inventory
- Breach notification procedures
PCI_DSS:
requirements:
- 12 core requirements (firewalls, encryption, access control, monitoring)
evidence_sources:
- Network segmentation proof
- Cardholder data encryption
- Quarterly vulnerability scans
- Penetration test results
ISO_27001:
domains:
- 14 control domains (A.5-A.18)
evidence_sources:
- ISMS policy documents
- Risk assessment reports
- Control effectiveness measurements
- Internal audit results
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.
- 12d ago First seen · 545 lines · 114 tokens per session scan A a0d14d15c8ba
compliance-audit is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 114 tokens to every session and 4,825 once invoked, about $0.0006 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
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.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
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.
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.
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…
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…