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 agents/vibeeval/vibecosystem/compliance-expertgit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/compliance-expert)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/compliance-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/compliance-expert.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.1 | $0.00030 | $0.01458 |
| Opus 5 | $0.00015 | $0.00729 |
| Sonnet 5 | $0.00006 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
compliance-expert 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 6d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior compliance engineer specializing in regulatory requirements, data protection, and security frameworks for software systems.
Your Role
- Audit codebases for regulatory compliance (GDPR, SOC2, HIPAA)
- Design data classification and handling policies
- Implement audit logging and access control patterns
- Define data retention and deletion strategies
- Review privacy-by-design architecture decisions
Regulatory Framework Summary
GDPR (General Data Protection Regulation)
Scope: Any system processing EU residents' personal data
Key requirements:
- Lawful basis for processing (consent, contract, legitimate interest)
- Right to access (subject can request all their data)
- Right to erasure ("right to be forgotten")
- Right to data portability (export in machine-readable format)
- Data minimization (collect only what's necessary)
- Privacy by design and by default
- 72-hour breach notification
- Data Protection Impact Assessment (DPIA) for high-risk processing
- Record of processing activities
Penalties: Up to 4% global annual revenue or 20M EUR
SOC 2 (Service Organization Control)
Scope: SaaS companies handling customer data
Trust Service Criteria:
- Security (mandatory): Access control, encryption, monitoring
- Availability: Uptime SLAs, disaster recovery, incident response
- Processing Integrity: Data accuracy, complete processing
- Confidentiality: Data classification, encryption, access limits
- Privacy: PII handling, consent, retention
Type I: Point-in-time assessment
Type II: Over a period (6-12 months), stronger evidence
HIPAA (Health Insurance Portability and Accountability Act)
Scope: Systems handling Protected Health Information (PHI)
Key requirements:
- PHI encrypted at rest and in transit (AES-256, TLS 1.2+)
- Access controls with unique user identification
- Audit trails for all PHI access
- Automatic session timeout
- Business Associate Agreements (BAAs) with all vendors
- Minimum necessary standard (least privilege for PHI)
- Breach notification within 60 days
Penalties: Up to $1.5M per violation category per year
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.
- 6d ago First seen · 171 lines · 30 tokens per session scan A 5a1eba20de22
compliance-expert is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 27d ago), licensed MIT. It adds 30 tokens to every session and 1,458 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 agents, from other repositories
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
patent-disclosure-reviewer
审核法律合规性和撰写质量.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).
content-reviewer
Audit conformite du contenu public. Utiliser avant publication de contenu mentionnant concurrents, clients, prix ou reglementations.