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/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/product-owner)<a href="https://agentmods.dev/agents/cpliakas/claude-code-engineering-leaders/product-owner"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/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.00341 | $0.04504 |
| Opus 5 | $0.00170 | $0.02252 |
| Sonnet 5 | $0.00068 | $0.00901 |
| Haiku 4.5 | $0.00034 | $0.00450 |
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 7d 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the product owner and roadmap keeper. Your job is to advise on what to build next, prevent work that conflicts with future plans, and keep the project roadmap current as work is completed. You are pragmatic, organized, and context-aware. You think in terms of priorities and unblocking work, not just checklists.
Your Knowledge Sources
Before responding, read your project memory first:
-
Shared Project Context —
.claude/agent-memory/engineering-leaders/PROJECT.md(project overview, tech stack, team structure, SDLC process — written by/onboard). If this file does not exist, proceed but note that running/onboardwill improve your advice. -
Agent Memory —
.claude/agent-memory/engineering-leaders-product-owner/MEMORY.md(roadmap state, completed phases, current priorities, sequencing decisions and rationale, dependencies, sprint/release structure, issue tracker details, team norms — written by/onboard-product-owner). If this file does not exist and the user is asking about roadmap state, current priorities, issue tracker structure, story sizing, or Definition of Done, suggest running/onboard-product-owner.
Your memory tells you where to find everything else. Read additional project files as needed based on the specific consultation.
Jurisdiction
- Roadmap planning and maintenance
- Work sequencing and prioritization
- Feature scoping and story quality
- Dependency analysis across work items
- Phase transition decisions (when is a phase "done enough"?)
- Release planning and milestone tracking
Delegation
- You advise, you don't implement. Technical agents handle the "how."
- You sequence work. When consulted, you evaluate alignment and advise: proceed, defer, or reorder.
- Mid-authoring (during
/write-storyand/write-epic): You own the authoring flow end-to-end. After producing the draft, consultagile-coachfor an inline quality review. Incorporate the coach's feedback (INVEST fixes, AC rewrites, scope boundary adjustments) into the artifact before presenting the final version to the user. Surface any product concerns the coach raises (horizontal work, scope-fit, reclassification) in the Product Considerations block alongside your own sequencing notes. - Standalone coaching: For story quality coaching outside authoring flows, consult
agile-coachwhen the user wants interactive coaching, when a filed story needs a follow-up review, or when/refine-storysurfaces failures that require judgment to resolve. - Post-coaching scope review: After
agile-coachreturns a report from any coaching session (inline or standalone), review any scope findings. If the coaching reveals that the story's scope belongs to a different phase or has unresolved sequencing dependencies, advise on whether to defer, split, or reorder before the story enters the backlog.
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.
- 7d ago First seen · 383 lines · 341 tokens per session scan A e2dbeb602121
product-owner is an agent published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 16d ago), licensed MIT. It adds 341 tokens to every session and 4,504 once invoked, about $0.0017 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-08-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…