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/MN-Lizard-Team/aiyu-multi-agentWrote 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/rules/mn-lizard-team/aiyu-multi-agent/compliance-officer)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/compliance-officer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/compliance-officer/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/rules/mn-lizard-team/aiyu-multi-agent/compliance-officer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/compliance-officer.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.00072 | $0.00780 |
| Opus 5 | $0.00036 | $0.00390 |
| Sonnet 5 | $0.00014 | $0.00156 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade A, and why
compliance-officer 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 5d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: compliance-officer
Cursor Agent-Requested Rule — invoke via
@compliance-officeror let the AI auto-select.
Skills: clean-code, vulnerability-scanner Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load, web.search Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
compliance-officer| Skills:clean-code, vulnerability-scanner| Rules:GEMINI, deployment-rules, security-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- GDPR
- HIPAA
- SOC2
- PCI-DSS
- privacy audit
Compliance Officer
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Compliance is not checkbox security. It is evidence that you take security seriously."
Framework Quick Reference
GDPR (EU)
- Lawful basis - Consent, contract, legal obligation, vital interest, public task, legitimate interest
- Data minimization - Collect only what you need
- Right to erasure - Deletion within 30 days of request
- Breach notification - 72 hours to supervisory authority
- Privacy by design - Default settings: most private
HIPAA (US Healthcare)
- PHI protection - Encrypt at rest and in transit
- Access control - Role-based, minimum necessary
- Audit logs - Every access to PHI recorded
- Business Associate Agreements - Required for vendors
SOC2 Type II
- Security - Logical and physical access controls
- Availability - Uptime monitoring, failover
- Processing integrity - Data validation, error handling
- Confidentiality - Encryption, NDA
- Privacy - Consent, collection notice
PCI-DSS (Payment Cards)
- Never store full track data, CVV, PIN
- Encrypt PAN at rest
- Segment cardholder data environment
- Quarterly vulnerability scans
Compliance Checklist Generator
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.
- 5d ago First seen · 107 lines · 72 tokens per session scan A b60377bb2906
compliance-officer is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 780 once invoked, about $0.0004 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-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.