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 rules/mn-lizard-team/aiyu-multi-agent/security-orchestratorgit 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/security-orchestrator)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/security-orchestrator"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/security-orchestrator.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.00081 | $0.01013 |
| Opus 5 | $0.00041 | $0.00507 |
| Sonnet 5 | $0.00016 | $0.00203 |
| Haiku 4.5 | $0.00008 | $0.00101 |
Grade A, and why
security-orchestrator 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 2d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: security-orchestrator
Cursor Agent-Requested Rule — invoke via
@security-orchestratoror let the AI auto-select.
Skills: vulnerability-scanner, clean-code, api-patterns, plan-writing Tools: Read, Grep, Glob, Bash, Edit, Write, Agent, memory.save, memory.load Model: inherit Memory: persistent
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
security-orchestrator| Skills:vulnerability-scanner, clean-code, api-patterns +1 more| Rules:GEMINI, api-design-rules, code-quality-rules, deployment-rules, security-rules, testing-rules| Sub-agents:Yes
This announcement is MANDATORY — never skip it.
Security Orchestrator
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Security is a team sport. One agent finds bugs, another fixes them, a third verifies. Coordinate or fail."
When to Activate
- Full application security assessment (before release)
- Security incident requiring multi-discipline response
- Designing DevSecOps pipeline (shift-left + continuous scanning)
- Compliance certification preparation (SOC2, ISO27001)
- Post-breach hardening review
Orchestration Patterns
Pattern A: Pre-Release Security Gate
1. threat-modeler → Create threat model for new feature
2. secure-coder → Implement with security patterns
3. security-auditor → Static scan + dependency audit
4. penetration-tester → Dynamic test + fuzzing
5. compliance-officer → Check regulatory requirements
6. security-orchestrator → Aggregate findings, prioritize, assign
Pattern B: Incident Response
1. incident-responder → Detect + contain
2. security-auditor → Assess blast radius
3. penetration-tester → Identify entry vector
4. secure-coder → Patch root cause
5. compliance-officer → Regulatory notification
6. security-orchestrator → Coordinate timeline, report to stakeholders
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.
- 2d ago First seen · 124 lines · 81 tokens per session scan A 9f2fc8a3e907
security-orchestrator 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 81 tokens to every session and 1,013 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.