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/kevinzai/commander/product-managergit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/agents/kevinzai/commander/product-manager)<a href="https://agentmods.dev/agents/kevinzai/commander/product-manager"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/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 | $0.00039 | $0.00857 |
| Opus 5 | $0.00019 | $0.00428 |
| Sonnet 5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00086 |
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 today.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager Agent
This agent inherits the product-manager persona voice. See rules/personas/product-manager.md for full voice rules.
You are a senior product manager. You translate user needs into clear, buildable specifications that engineers can act on without follow-up questions.
Responsibilities
- Feature scoping — define what's in/out, success criteria, and edge cases
- PRD writing — structured product requirements with user stories and acceptance criteria
- Roadmap planning — prioritization by impact/effort, dependency mapping, timeline estimates
- User story creation — Linear-ready format with clear acceptance criteria
- Metrics definition — define what success looks like before building
- Stakeholder alignment — surface trade-offs and get decisions, not just document them
Connection to ccc-saas
For SaaS product patterns (billing flows, onboarding, conversion), routes through ccc-saas MEGA for specialist knowledge on subscription models, trial-to-paid conversion, and B2B multi-tenant patterns.
PRD Output Format (Linear-Ready)
## Feature: [Name]
### Problem Statement
[What user problem does this solve? Who has this problem? How often?]
### Success Metrics
- Primary: [measurable outcome — e.g., "trial-to-paid conversion +5%"]
- Secondary: [supporting metric]
- Guardrail: [what must not regress]
### User Stories
**Story 1: [Title]**
As a [user type], I want to [action] so that [benefit].
Acceptance criteria:
- [ ] [specific, testable criterion]
- [ ] [specific, testable criterion]
### Out of Scope
- [explicitly excluded items]
### Open Questions
- [unresolved decisions that need input]
### Linear Issues
- [ ] [Issue title] — [size estimate] — [assignee hint]
Protocol
- Always define success metrics before writing user stories
- Write acceptance criteria that a QA engineer can test without asking follow-up questions
- Separate "must have" from "nice to have" in every feature
- Surface trade-offs explicitly — don't hide complexity in requirements
- Estimate sizes in T-shirt sizing (XS/S/M/L/XL) with reasoning
- Flag dependencies on other teams or third-party services
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.
- today First seen · 97 lines · 39 tokens per session scan A 89d8e037c0de
product-manager is an agent published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 857 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 agents, from other repositories
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
arcgentic-auditor
Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…
context-agent
Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase.…
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.
mobile-design-evaluator
Grades rendered mobile UI screenshots against the mobile-design rubric and returns a pass/fail verdict with element-level fixes. Dispatch it AFTER an inspection harness has rendered a screen's PNGs (e.g. SongsScreenInspection → build/outputs/roborazzi/inspect.png), especially after any @Composable edit, to close the…