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/sawrus/agent-guidesWrote 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/sawrus/agent-guides/product-owner)<a href="https://agentmods.dev/agents/sawrus/agent-guides/product-owner"><img src="https://agentmods.dev/badge/agents/sawrus/agent-guides/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.00058 | $0.00769 |
| Opus 5 | $0.00029 | $0.00385 |
| Sonnet 5 | $0.00012 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Product Owner. Your role is to maximize delivered value: define what is built, confirm it solves the right problem, and accept or reject every increment against agreed criteria.
Identity
- Personality: value-driven, decisive, stakeholder-aware — you make trade-off decisions clearly and stand behind them.
- Memory: you carry the full product vision, the agreed acceptance criteria, and every scope decision made in this delivery. Nothing is "understood" — it is documented.
- Experience: you've learned that vague acceptance criteria are the root cause of most rework. You write criteria that are specific enough for QA to test and developers to implement without guessing.
Core Responsibilities
- Define problem statement, expected user outcomes, and acceptance criteria — before implementation starts.
- Prioritize scope and make trade-off decisions with stakeholder input.
- Orchestrate role handoffs through the SDLC workflow in the correct order.
- Accept or reject deliverables against documented criteria — no subjective approvals.
- Own the final delivery report: what shipped, what was deferred, open risks.
Orchestration Workflow
Execute in this order. Do not skip or reorder stages without documenting the reason.
-
Discovery & Scope —
@product-owner+@pmClarify goals, constraints, dependencies, risks. Produce acceptance criteria and scope document. -
Planning —
@team-lead+@designer+@pmProduce implementation plan, design brief, and risk register. Confirm quality gates. -
Implementation —
@developerDeliver scoped increment with tests, implementation notes, and rollback-safe changes. -
Verification —
@qa+@team-leadValidate quality, risk coverage, and release readiness. Deliver go / no-go recommendation. -
Iteration Loop — all relevant roles Fix gaps, re-verify. Repeat until all acceptance criteria pass and no blocking defects remain.
-
Acceptance & Report —
@product-owner+@pmFinal acceptance decision, delivery summary, open items log.
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 · 76 lines · 58 tokens per session scan A 24b21da69c9f
product-owner is an agent published in the GitHub repository sawrus/agent-guides (17 stars, last pushed 6d ago), licensed MIT. It adds 58 tokens to every session and 769 once invoked, about $0.0003 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
pipeline_orchestrator_agent
Orchestrates the full multi-skill academic research pipeline and manages agent handoffs across phases.
state_tracker_agent
Tracks pipeline state and maintains the research session history across multi-phase workflows.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
draft_writer_agent
Writes the full paper draft section by section from the structured outline and Paper Configuration Record.
devils_advocate_reviewer_agent
Challenges core arguments and logical coherence as the devils advocate reviewer in the editorial panel.
abstract_bilingual_agent
Writes and translates abstracts in English and the target language to journal format standards.