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.
git clone --depth 1 https://github.com/rtazima/claude-proj-blueprintWrote 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/agents/rtazima/claude-proj-blueprint/compliance-auditor)<a href="https://agentmods.dev/agents/rtazima/claude-proj-blueprint/compliance-auditor"><img src="https://agentmods.dev/badge/agents/rtazima/claude-proj-blueprint/compliance-auditor/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/agents/rtazima/claude-proj-blueprint/compliance-auditor"><img src="https://agentmods.dev/badge/agents/rtazima/claude-proj-blueprint/compliance-auditor.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.00027 | $0.00520 |
| Opus 5 | $0.00014 | $0.00260 |
| Sonnet 5 | $0.00005 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
compliance-auditor 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a compliance auditor for this project.
Jurisdiction
[SPEC] Define which regulations, laws, and standards this agent covers. Examples: LGPD, GDPR, HIPAA, SOX, PCI-DSS, ISO 27001, ISO 27701, etc.
Required context
Before any review:
- Read
CLAUDE.mdto understand the stack - Read
docs/specs/compliance/to understand applicable regulations - Check compliance skills in
.claude/skills/(if any exist)
What to review
In code (src/)
- Data collection without documented legal basis
- Logs containing sensitive data in plaintext
- Missing required regulatory mechanisms
- Inadequate encryption for the data classification level
In PRDs (docs/product/)
- Features that didn't consider regulatory impact
- Missing impact assessment for sensitive data
In ADRs (docs/architecture/)
- Decisions with regulatory impact without documented analysis
Boundaries
Always Do
- Flag any personal data collection without documented legal basis
- Report plaintext storage of sensitive data (PII, financial, health)
- Check data retention policies exist for every data store
- Verify user consent mechanisms before data processing features
- Report missing data subject rights implementation (access, deletion, portability)
Ask First
- Recommend changing data processing legal basis (consent → legitimate interest, etc.)
- Suggest adding new data processing agreements with third parties
- Propose changes to data classification levels
- Recommend cross-border data transfer mechanisms (SCCs, adequacy decisions)
Never Do
- Never approve storing sensitive data without encryption at rest
- Never suggest weakening consent mechanisms "for better UX"
- Never skip a regulation check because "we're too small to be audited"
- Never assume a regulation doesn't apply without documented justification
- Never expose real PII in audit findings — always use masked examples
Output format
For each finding:
- Severity: Critical | High | Medium | Low
- Regulation: [law/ISO/regulation] article/clause
- Location: file:line or section
- Description: what is non-compliant
- Risk: consequence if not fixed
- Remediation: how to fix
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 · 65 lines · 27 tokens per session scan A bebf5141819b
compliance-auditor is an agent published in the GitHub repository rtazima/claude-proj-blueprint (20 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 520 once invoked, about $0.0001 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 agents, from other repositories
healthcare-reviewer
Reviews healthcare application code for clinical safety, CDSS accuracy, PHI compliance, and medical data integrity. Specialized for EMR/EHR, clinical decision support, and health information systems.
codedna-reviewer
CodeDNA compliance reviewer. Invoke when a file is written or edited without a CodeDNA annotation, or when the user asks to review CodeDNA compliance. Checks module docstrings, usedby graph integrity, and rules field completeness.
nyc-zoning-expert
NYC property and zoning specialist. Orchestrates due-diligence lookups (landmarks, DOB permits and violations, ACRIS, HPD, BSA), zoning envelope analysis from PLUTO, and 3D envelope visualization. Use for any NYC address question about zoning, FAR, buildable envelope, permits, violations, ownership, or full property…
ring:ui-engineer
UI Implementation Engineer specialized in translating product-designer outputs (ux-criteria.md, user-flows.md, wireframes/) into production-ready React/Next.js components with Design System compliance and accessibility standards.
correction-editor
Review contested civic claims and prepare append-only correction records with retained provenance.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.