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 mostafa-drz/claude-skills --skill compliance-auditgit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/compliance-audit)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/compliance-audit"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/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/mostafa-drz/claude-skills/compliance-audit"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/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.00074 | $0.02783 |
| Opus 5 | $0.00037 | $0.01392 |
| Sonnet 5 | $0.00015 | $0.00557 |
| Haiku 4.5 | $0.00007 | $0.00278 |
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 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Audit
Scan a codebase directory (single repo, multi-repo, or monorepo) against a compliance framework. Each subdirectory gets a parallel audit agent. Output is a structured markdown report where every finding references specific code lines.
Preferences
On startup, use Read to load ~/.claude/skills/compliance-audit/preferences.md. If it does not exist, treat as "no preferences set".
Context
On startup, use Bash to detect:
- Current working directory
- Whether the target directory is a git repo (and its remote URL for code references)
- Directory structure: list top-level subdirectories, identify monorepo packages or multi-repo layout
- Tech stacks present: look for package.json, requirements.txt, Cargo.toml, go.mod, Dockerfile, .env files, etc.
Skip any detection that fails.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete~/.claude/skills/compliance-audit/preferences.md, confirm, stop- anything else → parse arguments and run the audit
Help
Compliance Audit — Scan codebases against compliance frameworks
Usage:
/compliance-audit <standard> Audit current directory
/compliance-audit <standard> --dir <path> Audit a specific directory
/compliance-audit <standard> --output <path> Write report to specific path
/compliance-audit <standard> --severity <level> Filter by minimum severity
/compliance-audit config Set preferences
/compliance-audit reset Clear preferences
/compliance-audit help This help
Standards:
SOC2, HIPAA, PCI-DSS, GDPR, ISO27001, NIST-CSF, OWASP, CIS, FedRAMP
(or any compliance framework — latest requirements fetched from web)
Severity levels:
critical, high, medium, low (default: low — shows everything)
Examples:
/compliance-audit SOC2
/compliance-audit HIPAA --dir ./backend --output ./reports
/compliance-audit PCI-DSS --severity high "focus on payment processing modules"
/compliance-audit GDPR "check data retention and consent flows"
Current preferences:
(read from ~/.claude/skills/compliance-audit/preferences.md)
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 · 292 lines · 74 tokens per session scan A a5a9258c8a69
compliance-audit is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 2,783 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
legal-discovery
Audit e-discovery and litigation document review systems -- data collection pipelines (PST, MBOX, SharePoint, Slack), document processing (OCR via Tesseract/ABBYY, metadata extraction, deduplication), Technology Assisted Review (TAR 1.0/2.0/CAL with recall/precision tracking).
litigation-predictor
Audit litigation analytics and case outcome prediction systems -- ML outcome models (logistic regression, gradient boosting, neural nets with temporal train/test splits), settlement range modeling (Monte Carlo simulation, comparable case matching, BATNA analysis).
sales-readiness
Audit whether a product is ready for enterprise sales. Use when you need to assess SSO/SAML/SCIM support, RBAC maturity, multi-tenancy data isolation, audit logging coverage, public API quality, SLA operational readiness, SOC2/ISO27001 certification gaps, GDPR data residency controls.
audit-support
Analyzes audit readiness systems for internal control testing, evidence collection workflows, statistical sampling methodology, audit finding documentation, and remediation tracking using PCAOB, ISA, and SOX compliance frameworks..
case-outcome-predictor
Audit legal case prediction systems for bias, fairness, accuracy, and ethical guardrails. Use when: 'check my prediction model for bias', 'audit case outcome fairness', 'evaluate legal ML model', 'review sentencing prediction ethics', 'analyze bail risk algorithm', 'fairness metrics for justice system AI'.
contract-risk
Audit contract management codebases for clause extraction accuracy, obligation tracking completeness, risk scoring model quality, renewal management, SLA monitoring, liability exposure, force majeure handling, and IP assignment detection..