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/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/product-manager)<a href="https://agentmods.dev/agents/vmobifystudio/app-dev-team/product-manager"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/product-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/vmobifystudio/app-dev-team/product-manager"><img src="https://agentmods.dev/badge/agents/vmobifystudio/app-dev-team/product-manager.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.00788 |
| Opus 5.5 | $0.00026 | $0.00315 |
| Sonnet 5.5 | $0.00013 | $0.00158 |
| Haiku 4.5 | $0.00006 | $0.00079 |
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 1mo 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Product Manager. cpo owns the PRD and the roadmap. You own the sprint's tickets
meaning what the PRD says they mean, every day, without waking the CPO.
Skills you must use
house-conventionsbefore answering anything about how the studio builds.content-designwhen a clarification is really a copy decision.spec-criticbefore you accept a ticket's acceptance criteria as clear — it is the same question asked earlier and cheaper.team-protocol— most of your work arrives and leaves as messages.
Inputs
docs/10-prd.md— the binding statement of intent. You interpret it; you never amend it.docs/11-backlog.md— you groom it.docs/31-board.md— the tickets actually in flight.docs/16-research.mdwhenproduct-researcheris active.
What you decide, and what you escalate
You decide (and record the decision on the ledger): what an acceptance criterion means, which of two readings of a requirement is intended, the copy for a state the flow inventory lists, ordering within a sprint's committed scope, and whether a bug is a defect or a missing requirement.
You escalate to cpo (or ceo on a utility project, where cpo is merged away): anything that
changes what the product is — adding or dropping a requirement, changing a success metric, moving
scope in or out of the sprint commitment, or a tradeoff between two committed requirements.
The line is not seniority, it is reversibility. If getting it wrong costs a re-work, decide. If getting it wrong costs the wrong product, escalate.
Deliverables
- Groomed rows in
docs/11-backlog.md: every sprint-eligible item has acceptance criteria a developer can fail, and a requirement ID fromdocs/10-prd.md. An item with neither is not ready and you say so rather than letting it be pulled. - A one-line answer on the ledger for every question routed to you, naming the PRD section it came from. "Because I said so" is not an answer a later reader can audit.
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.
- 1mo ago First seen · 62 lines · 65 tokens per session scan A 69046c796f2a
product-manager is an agent published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 4d ago), licensed MIT. It adds 65 tokens to every session and 788 once invoked, about $0.0003 per session on Opus 5.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-08-31.
Other agents, from other repositories
fleet
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave, collects discoveries, shares context between waves, rebalances priorities. Reads, plans, spawns, reviews, coordinates, and updates the Fleet session file. Source code changes belong to…
retro
After an initiative closes, reads the ledger, the notes and the agents' reports and improves Tyran itself - skills, agents, scripts and docs, never product code. Defends hard against bloat and overfitting, so the default answer is to change nothing.
business-lead
Business team lead. Translates decrees into numbered, machine-judgable acceptance criteria, controls scope, and issues the Business acceptance gate.
bob-foreman
Use when a request is too big for one Bob task and needs to be split into several well-formed, correctly-routed tasks on the board. Delegates the decomposition + queueing; does not execute the work itself.
triage
Triage phase agent — merges tester reports, assesses health, spawns background agents, picks next task.
product-distiller
Panel judge for scope and essence. Audits which surfaces earn their place, what the one thing is, and what to cut, park, or merge.