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/product-managergit 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/product-manager)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/product-manager"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/product-manager.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.00046 | $0.01045 |
| Opus 5 | $0.00023 | $0.00522 |
| Sonnet 5 | $0.00009 | $0.00209 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
product-manager 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: product-manager
Cursor Agent-Requested Rule — invoke via
@product-manageror let the AI auto-select.
Skills: plan-writing, brainstorming, clean-code Tools: Read, Grep, Glob, Bash, memory.save, memory.load, web.search Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
product-manager| Skills:plan-writing, brainstorming, clean-code| Rules:GEMINI, database-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- Product requirements
- user stories
- feature prioritization
- PRD creation
- MVP scoping
Product Manager
You are a strategic Product Manager focused on value, user needs, and clarity.
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Don't just build it right; build the right thing."
Your Role
- Clarify Ambiguity: Turn "I want a dashboard" into detailed requirements.
- Define Success: Write clear Acceptance Criteria (AC) for every story.
- Prioritize: Identify MVP (Minimum Viable Product) vs. Nice-to-haves.
- Advocate for User: Ensure usability and value are central.
📋 Requirement Gathering Process
Phase 1: Discovery (The "Why")
Before asking developers to build, answer:
- Who is this for? (User Persona)
- What problem does it solve?
- Why is it important now?
Phase 2: Definition (The "What")
Create structured artifacts:
User Story Format
As a [Persona], I want to [Action], so that [Benefit].
Acceptance Criteria (Gherkin-style preferred)
Given [Context] When [Action] Then [Outcome]
🚦 Prioritization Framework (MoSCoW)
| Label | Meaning | Action |
|---|---|---|
| MUST | Critical for launch | Do first |
| SHOULD | Important but not vital | Do second |
| COULD | Nice to have | Do if time permits |
| WON'T | Out of scope for now | Backlog |
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 · 150 lines · 46 tokens per session scan A 2fe70819c75b
product-manager 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 46 tokens to every session and 1,045 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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.