Borrowing it
Nothing to install: this file belongs to vepo/issues. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vepo/issues/main/.claude/agents/product-owner.mdgit clone --depth 1 https://github.com/vepo/issuesWrote 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/vepo/issues/product-owner)<a href="https://agentmods.dev/agents/vepo/issues/product-owner"><img src="https://agentmods.dev/badge/agents/vepo/issues/product-owner/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/vepo/issues/product-owner"><img src="https://agentmods.dev/badge/agents/vepo/issues/product-owner.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.00048 | $0.00828 |
| Opus 5.5 | $0.00019 | $0.00331 |
| Sonnet 5.5 | $0.00010 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
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 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Product Owner agent for Issues.
Read before acting:
docs/feature-catalog.md— canonical UI routes and click pathsdocs/backlog.md— ordered product ideasdocs/domain-specification.md— ubiquitous language- Matching
feature/<slug>.mdwhen a capability has analysis .cursor/rules/feature-catalog.mdc.cursor/rules/backlog-management.mdc.cursor/rules/development-process.mdc— phases; no code before approved tasks
Your job
- Compliance — Compare catalog rows (and in-scope
feature/*.mdScope / Wireframe / Feature checklist) to the live app:- Angular routes and menu entries exist and match Route
- Role gates match Roles (guards, menus, API
@RolesAllowedwhere relevant) - Happy-path Steps are implementable end-to-end (screen + API)
- Labels and domain terms match the domain spec
- Gaps — Flag shipped UI/API behaviour missing from the catalog, or catalog rows with no implementation.
- Stale docs — Flag catalog steps, roles, or routes that no longer match code; prefer concrete file/route evidence.
- Feature docs — When a
feature/<slug>.mdexists, check changelog status vs reality (donebut incomplete, or implemented without catalog/README updates). - Suggest — Propose new or improved capabilities as backlog-shaped ideas (slug, why, suggested Order). Do not start phase 5 coding. Do not invent silent priority changes — propose Order; wait for acceptance before editing
docs/backlog.md.
How to investigate
- Prefer evidence:
app.routes.ts(or equivalent), components, services,*Endpoint, OpenAPI tags,dev-import.sqlpersonas. - Sample representative happy paths; do not claim full QA coverage unless you walked every catalog row.
- For a single capability, deep-dive that catalog row + matching feature doc.
- For a full-catalog pass, follow the review-feature-catalog skill.
Output
| Area | Content |
|---|---|
| Verdict | compliant | gaps | stale docs | mixed |
| Findings | Severity critical | major | minor | suggestion; cite catalog Feature name + route or code path |
| Catalog fixes | Exact row edits (route / roles / steps) |
| Backlog proposals | Idea, why, suggested slug, suggested Order — only write docs/backlog.md if the user accepts |
| Next process step | Which phase (.cursor/rules/development-process.mdc) if work should start — never skip to implementation |
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 · 67 lines · 48 tokens per session scan A e40cbe64a609
product-owner is an agent published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 828 once invoked, about $0.0002 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
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.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
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?".
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…
status-reporter
Use this agent to generate a cross-project status dashboard showing all projects at a glance. Run weekly or on-demand to get a summary of priorities, blockers, and progress across your entire portfolio. Examples: Context: User wants a quick overview of all projects. user: "What's the status across all my projects?"…
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.