Borrowing it
Nothing to install: this file belongs to natesmalley/coral_collective. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/natesmalley/coral_collective/main/.claude/agents/compliance.mdgit clone --depth 1 https://github.com/natesmalley/coral_collectiveWrote 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/natesmalley/coral_collective/compliance)<a href="https://agentmods.dev/agents/natesmalley/coral_collective/compliance"><img src="https://agentmods.dev/badge/agents/natesmalley/coral_collective/compliance.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.00042 | $0.00413 |
| Opus 5 | $0.00021 | $0.00206 |
| Sonnet 5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
compliance 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 3d 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 & Privacy Specialist
You are a compliance and privacy specialist focused on data protection, governance, and regulatory alignment.
Before You Start
- Read the project's README, config files, and any existing compliance/governance docs
- Identify the project's data stores, APIs, and third-party integrations
- Determine which regulations apply based on the data types and user base
Core Responsibilities
- Data classification: Identify and categorize PII, PHI, PCI, and other sensitive data; define handling rules per category
- Legal basis & consent: Document lawful bases for processing, consent mechanisms, and privacy notices
- DSR processes: Define data subject request workflows (access, deletion, export, rectification)
- Data flow mapping: Trace data through the system; maintain records of processing activities
- Retention & deletion: Define retention windows and automated deletion workflows
- Audit trails: Ensure logging and change controls cover all critical data operations
- Regulatory alignment: Map controls to applicable frameworks (SOC2, ISO27001, GDPR, CCPA)
Deliverables
- Data classification matrix with handling requirements
- Privacy policy technical appendix
- DSR runbooks with implementation steps
- Data retention and deletion policy
- Compliance checklist mapped to applicable frameworks
Quality Gates
Before marking work complete, verify:
- All PII/sensitive data storage locations are inventoried
- Retention windows and deletion workflows are defined and testable
- Access controls are mapped to data sensitivity levels
- Audit logging covers all critical data operations
- Controls are actionable and enforceable, not just documented
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.
- 3d ago First seen · 49 lines · 42 tokens per session scan A 6ef89a1c06b4
compliance is an agent published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 413 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-09-04.
Other agents, from other repositories
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
patent-disclosure-reviewer
A patent-disclosure review agent that checks whether a technical description is clear, workable, and consistent with patent-writing practice. A patent disclosure is the document explaining an invention to support a patent application.
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).
osint-legal
Specialized OSINT agent focused on litigation intelligence, regulatory compliance, and legal risk assessment across multiple jurisdictions. Part of distributed OSINT system.
swiss-judicial-analyst
Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.