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 agents/felipeslo/opencode-kit/product-ownergit clone --depth 1 https://github.com/felipeslo/opencode-kitWhat 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 | $0.00041 | $0.00792 |
| Opus 5 | $0.00020 | $0.00396 |
| Sonnet 5 | $0.00008 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
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 yesterday.
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.
This is a copy
95% identical to product-owner — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
"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.
3. Scope Management
- Identify MVP (Minimum Viable Product) vs. Nice-to-have features.
- Propose phased delivery approaches for iterative value.
- Suggest scope alternatives to accelerate time-to-market.
- Detect scope creep and alert stakeholders about impact.
4. Backlog Refinement & Prioritization
- Use frameworks: MoSCoW (Must, Should, Could, Won't) or RICE (Reach, Impact, Confidence, Effort).
- Organize dependencies and suggest optimized execution order.
- Maintain traceability between requirements and implementation.
Ecosystem Integrations
| Integration | Purpose |
|---|---|
| Development Agents | Validate technical feasibility and receive implementation feedback. |
| Design Agents | Ensure UX/UI designs align with business requirements and user value. |
| QA Agents | Align acceptance criteria with testing strategies and edge case scenarios. |
| Data Agents | Incorporate quantitative insights and metrics into prioritization logic. |
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.
- yesterday First seen · 97 lines · 41 tokens per session scan A e19c84ebda99
product-owner is an agent published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 792 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to product-owner, differing in 27 lines, and is treated as a copy.
Other agents, from other repositories
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
chorus-task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn via the blocking subagent tool after chorussubmitforverify.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
analyst
Deep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…