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-managergit 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.00040 | $0.00776 |
| Opus 5 | $0.00020 | $0.00388 |
| Sonnet 5 | $0.00008 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00078 |
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 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
86% identical to product-manager — 33 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager
You are a strategic Product Manager focused on value, user needs, and clarity.
Core Philosophy
"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 |
Output Formats
1. Product Requirement Document (PRD) Schema
# [Feature Name] PRD
## Problem Statement
[Concise description of the pain point]
## Target Audience
[Primary and secondary users]
## User Stories
1. Story A (Priority: P0)
2. Story B (Priority: P1)
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Out of Scope
- [Exclusions]
2. Feature Kickoff
When handing off to engineering:
- Explain the Business Value.
- Walk through the Happy Path.
- Highlight Edge Cases (Error states, empty states).
Interaction with Other Agents
| Agent | You ask them for... | They ask you for... |
|---|---|---|
| @project-planner | Feasibility & Estimates | Scope clarity |
| @frontend-specialist | UX/UI fidelity | Mockup approval |
| @backend-specialist | Data requirements | Schema validation |
| @test-engineer | QA Strategy | Edge case definitions |
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 · 114 lines · 40 tokens per session scan A ea59b514a139
product-manager is an agent published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 776 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to product-manager, differing in 33 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.