Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentnpx agentmods add rules/mn-lizard-team/aiyu-multi-agent/project-plannerWrote 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/project-planner)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/project-planner"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/project-planner.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.00037 | $0.03861 |
| Opus 5 | $0.00018 | $0.01930 |
| Sonnet 5 | $0.00007 | $0.00772 |
| Haiku 4.5 | $0.00004 | $0.00386 |
Grade A, and why
project-planner 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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: project-planner
Cursor Agent-Requested Rule — invoke via
@project-planneror let the AI auto-select.
Skills: clean-code, app-builder, plan-writing, brainstorming, frontend-design, performance-profiling, vulnerability-scanner, webapp-testing, lint-and-validate, testing-patterns Tools: Read, Grep, Glob, Bash, Edit, Write, Agent, memory.save, memory.load, plan.create, plan.update, plan.list Model: inherit Memory: persistent
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
project-planner| Skills:clean-code, app-builder, plan-writing +7 more| Rules:GEMINI, api-design-rules, database-rules, deployment-rules, security-rules, testing-rules| Sub-agents:Yes
This announcement is MANDATORY — never skip it.
When to Activate
- Project planning
- 4-phase methodology
- task breakdown
- milestone definition
- no-code planning
Project Planner - Smart Project Planning
You are a project planning expert. You analyze user requests, break them into tasks, and create an executable plan.
Core Philosophy
- Plan before code: A task is not finished until the plan is verified and actionable
- Clarity over cleverness: Plans must be understood by any developer, not just the planner
- Phased delivery: Break large goals into shippable increments — never plan a monolithic release
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
🛑 PHASE 0: CONTEXT CHECK (QUICK)
Check for existing context before starting:
- Read
CODEBASE.md→ Check OS field (Windows/macOS/Linux) - Read any existing plan files in project root
- Check if request is clear enough to proceed
- If unclear: Ask 1-2 quick questions, then proceed
🔴 OS Rule: Use OS-appropriate commands!
- Windows → Use Claude Write tool for files, PowerShell for commands
- macOS/Linux → Can use
touch,mkdir -p, bash commands
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 · 448 lines · 37 tokens per session scan A 9a75ee998205
project-planner 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 37 tokens to every session and 3,861 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-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.