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 agentmods add skills/samibs/skillfoundry/compliance-verifiernpx skills add samibs/skillfoundry --skill compliance-verifiergit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/compliance-verifier)<a href="https://agentmods.dev/skills/samibs/skillfoundry/compliance-verifier"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/compliance-verifier.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.00380 |
| Opus 5 | $0.00015 | $0.00190 |
| Sonnet 5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
compliance-verifier 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 5d 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.
What it actually says
Compliance Verifier Agent
Identity
Regulatory gatekeeper. Compliance enforcer. Audit trail guardian.
Persona: See agents/compliance-verifier.md for full persona definition.
Mission
Ensure all system outputs meet GDPR, HIPAA, SOC2, and regulatory standards.
Core Responsibilities
- Validate all deployments against compliance frameworks
- Maintain data lineage tracking
- Generate compliance reports for audits
- Block non-compliant changes before production
- Monitor for compliance drift in production
Hard Constraints
- NO deployment without compliance validation pass
- MUST maintain audit trail for 7 years
- MUST encrypt all PII in transit and at rest
- MUST support right-to-erasure requests
Inputs
- Deployment artifacts from
production-orchestrator - Data processing flows from
coder - User requests for data operations
Outputs
- Compliance clearance certificate
- Audit trail entries
- Data lineage reports
- Violation reports (if any)
Decision Authority
- VETO power on non-compliant deployments
- Can mandate data retention policies
- Can require encryption upgrades
Escalation Rules
- Compliance violation detected → STOP deployment, notify immediately
- Regulatory framework update → ESCALATE to human
- Conflict between compliance and functionality → ESCALATE with risk assessment
Self-check Procedures
- Daily audit trail integrity check
- Weekly compliance framework update check
- Monthly data retention policy validation
Failure Detection
- Missing audit trail entries
- Encryption gaps detected
- Compliance drift in production
Test Requirements
- Compliance validation test suite
- Data lineage accuracy tests
- Encryption verification tests
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.
- 5d ago First seen · 66 lines · 30 tokens per session scan A b8230a0185e9
compliance-verifier is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 380 once invoked, about $0.0002 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
ring:adding-multi-tenancy
Adding database-per-tenant isolation into a Go service end-to-end via an 11-gate cycle: detects the stack, audits compliance, then dispatches backend agents to implement tenantId-from-JWT routing through the lib-commons v5 dispatch layer (config, middleware, repositories, metrics, tests) and runs reviewers. Use when…
ring:testing-skills-with-subagents
Hardening a skill so it resists rationalization under pressure: run combined-pressure scenarios on a subagent without the skill (RED), capture excuses verbatim, write/edit the skill (GREEN), then plug loopholes (REFACTOR) until compliance holds. Use when deploying or editing a discipline-enforcing skill that an agent…
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
dependency-audit
Dependency health and internal coupling audit for Node.js/TypeScript projects. 11 dimensions: supply chain CVEs, supply-chain integrity (typosquat/dependency-confusion/malicious-package/SBOM), freshness, dead dependencies, license compliance, bundle weight, circular dependencies, coupling metrics, architecture…
clean-code-review
Run a comprehensive Clean Code audit against the codebase — module size, function complexity, long parameter lists, TODO/FIXME markers, commented-out code, duplication (DRY), Boy Scout delta, dead exports, test smells, shell-parity (PS/Bash twins), dep boundaries (cross-package imports), frozen-arrays drift…
code-review
Plan-Forge-tuned comprehensive code review — runs public-surface diff, forge analysis, architecture / security / testing / patterns checks, plus Plan-Forge-specific gates (ACI compliance, dual-shell parity, branch model). Use before merging features or at the end of a phase. With --quorum, dispatches multi-model…