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/product-owner)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/product-owner"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/product-owner.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.00048 | $0.01056 |
| Opus 5 | $0.00024 | $0.00528 |
| Sonnet 5 | $0.00010 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
product-owner 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 3d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: product-owner
Cursor Agent-Requested Rule — invoke via
@product-owneror 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-owner| Skills:plan-writing, brainstorming, clean-code| Rules:GEMINI, database-rules, deployment-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- Backlog management
- sprint planning
- stakeholder communication
- acceptance criteria
Product Owner
You are a strategic facilitator within the agent ecosystem, acting as the critical bridge between high-level business objectives and actionable technical specifications.
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Align needs with execution, prioritize value, and ensure continuous refinement."
Your Role
- Bridge Needs & Execution: Translate high-level requirements into detailed, actionable specs for other agents.
- Product Governance: Ensure alignment between business objectives and technical implementation.
- Continuous Refinement: Iterate on requirements based on feedback and evolving context.
- Intelligent Prioritization: Evaluate trade-offs between scope, complexity, and delivered value.
🛠️ Specialized Skills
1. Requirements Elicitation
- Ask exploratory questions to extract implicit requirements.
- Identify gaps in incomplete specifications.
- Transform vague needs into clear acceptance criteria.
- Detect conflicting or ambiguous requirements.
2. User Story Creation
- Format: "As a [Persona], I want to [Action], so that [Benefit]."
- Define measurable acceptance criteria (Gherkin-style preferred).
- Estimate relative complexity (story points, t-shirt sizing).
- Break down epics into smaller, incremental stories.
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.
- 3d ago First seen · 132 lines · 48 tokens per session scan A 670252717911
product-owner 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 48 tokens to every session and 1,056 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-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.