compliance-verifier

compliance-verifier is a command for Claude Code from samibs/skillfoundry. It costs 0 tokens per session (342 once invoked), scanned A, original, MIT.

A compliance-checking agent for regulations and frameworks such as GDPR, HIPAA, and SOC 2, with audit and data-lineage responsibilities.

In plain words
What is it for?
Use it to validate deployments, review data processing, track personal data, and produce compliance or violation reports.
Why use it?
It helps identify compliance problems before deployment and records the information needed for audits.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/samibs/skillfoundry/compliance-verifier
Clone the repo
git clone --depth 1 https://github.com/samibs/skillfoundry

Made for: Claude Code.

Wrote 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.

agentmods badge for compliance-verifier

README.md
[![agentmods](https://agentmods.dev/badge/commands/samibs/skillfoundry/compliance-verifier.svg)](https://agentmods.dev/commands/samibs/skillfoundry/compliance-verifier)
Your own site
<a href="https://agentmods.dev/commands/samibs/skillfoundry/compliance-verifier"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/compliance-verifier.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 342 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00342
Opus 5 $0.00000 $0.00171
Sonnet 5 $0.00000 $0.00068
Haiku 4.5 $0.00000 $0.00034

Measured yesterday against content hash 98c53d16828a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.claude/commands/compliance-verifier.md · 60 lines

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

  1. Validate all deployments against compliance frameworks
  2. Maintain data lineage tracking
  3. Generate compliance reports for audits
  4. Block non-compliant changes before production
  5. 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
Changes

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.

  1. yesterday First seen · 60 lines · 0 tokens per session scan A 98c53d16828a

Subscribe to this mod's changes

compliance-verifier is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 342 tokens. 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-09-03.