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 commands/mn-lizard-team/aiyu-multi-agent/compliancegit 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/commands/mn-lizard-team/aiyu-multi-agent/compliance)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/compliance"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/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.00000 | $0.00478 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/compliance
Regulatory compliance and privacy audit — GDPR, HIPAA, SOC2, PCI-DSS checklist generation and gap analysis. Used when handling PII, preparing for certification, or designing consent flows.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `compliance-officer`** | Skills: `clean-code, vulnerability-scanner`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Behavior
- Follow the task steps defined below
- Apply the Socratic Gate: ask clarifying questions if requirements are unclear
- Report completion status at the end
/compliance — Regulatory Compliance Audit
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `compliance-officer`** | Skills: `clean-code, vulnerability-scanner`
Task
Evaluate compliance posture. Generate checklists, identify gaps, and guide remediation for major frameworks.
Supported Frameworks:
- GDPR — EU data protection
- HIPAA — US healthcare PHI
- SOC2 — Service organization controls
- PCI-DSS — Payment card industry
Steps:
-
Framework Selection
- Identify which regulations apply
- Determine data classification
-
Gap Analysis
- Audit current controls
- Map to framework requirements
- Identify missing controls
-
Checklist Generation
- Data handling, access control, audit logs
- Incident response, retention, consent
-
Remediation Plan
- Prioritize by compliance risk
- Assign to technical teams
- Set audit deadlines
Usage Examples
/compliance GDPR gap analysis
/compliance HIPAA checklist
/compliance prepare SOC2 audit
/compliance PCI-DSS requirements
/compliance privacy by design review
/compliance data retention policy
Caution
- Compliance != security — it is evidence of security
- Frameworks overlap — avoid duplicating controls
- Document decisions — auditors need proof
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 · 91 lines · 0 tokens per session scan A c3651e33ebd0
compliance is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 478 tokens. 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-31.
Other commands, from other repositories
dashboard-server-tunnel-status
Tunnel status + public URL. Runs locally, no LLM.
rn-feature-dev
Guided feature development for React Native — explore codebase, design architecture, implement, verify live on device, and review quality.
brainstorm
Command dispatcher for brainstorm.
plan
Command dispatcher for plan.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.