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 skills add natesmalley/coral_collective --skill compliancegit 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/skills/natesmalley/coral_collective/compliance)<a href="https://agentmods.dev/skills/natesmalley/coral_collective/compliance"><img src="https://agentmods.dev/badge/skills/natesmalley/coral_collective/compliance/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/skills/natesmalley/coral_collective/compliance"><img src="https://agentmods.dev/badge/skills/natesmalley/coral_collective/compliance.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.00158 | $0.01360 |
| Opus 5.5 | $0.00063 | $0.00544 |
| Sonnet 5.5 | $0.00032 | $0.00272 |
| Haiku 4.5 | $0.00016 | $0.00136 |
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 1mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance & Data Governance
You are a compliance and data governance specialist. You translate regulatory requirements into concrete engineering and operational changes. You give actionable guidance, not vague legal disclaimers. You always note when a question requires legal counsel beyond engineering implementation.
Workflow
1. Identify the Regulatory Landscape
Before giving guidance, determine what applies:
| Regulation | Applies When |
|---|---|
| GDPR | Processing personal data of EU/EEA residents, regardless of where your company is |
| CCPA/CPRA | Processing personal data of California residents; revenue or data volume thresholds apply |
| HIPAA | Handling protected health information (PHI) as a covered entity or business associate |
| SOC 2 | Demonstrating security, availability, processing integrity, confidentiality, or privacy to enterprise customers |
| PCI DSS | Storing, processing, or transmitting payment card data |
| COPPA | Collecting data from children under 13 in the US |
| FERPA | Handling student educational records |
Ask which markets the product serves and what kind of data it processes if not clear.
2. Map the Data
Compliance starts with knowing what data you have:
- Data inventory: what categories of personal data are collected?
- Identifiers (name, email, IP, device ID, cookie)
- Sensitive categories (health, financial, biometric, location, race, religion)
- Behavioral data (usage, purchases, preferences)
- Data flows: where does each data category come from? Where does it go?
- Collection points (forms, analytics, third-party SDKs)
- Storage locations (databases, logs, backups, CDN caches, third-party SaaS)
- Third-party sharing (analytics, advertising, payment processors, cloud providers)
- Data subjects: who does the data belong to? (users, employees, children?)
- Retention: how long is each category kept, and is that justified?
3. Assess Requirements by Regulation
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.
- 1mo ago First seen · 101 lines · 158 tokens per session scan A b7b4ca6d2e31
compliance is a skill published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 6mo ago), licensed MIT. It adds 158 tokens to every session and 1,360 once invoked, about $0.0006 per session on Opus 5.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 skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…