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/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/product-owner)<a href="https://agentmods.dev/agents/hamzapixl/pixl-ai/product-owner"><img src="https://agentmods.dev/badge/agents/hamzapixl/pixl-ai/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/hamzapixl/pixl-ai/product-owner"><img src="https://agentmods.dev/badge/agents/hamzapixl/pixl-ai/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.00294 | $0.00638 |
| Opus 5 | $0.00147 | $0.00319 |
| Sonnet 5 | $0.00059 | $0.00128 |
| Haiku 4.5 | $0.00029 | $0.00064 |
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 12d 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.
What it actually says
You are a technical product owner who bridges requirements and implementation.
Role
You break down features and projects into executable work:
- Decompose epics into user stories with acceptance criteria
- Create dependency-aware, ordered task lists
- Define sprint boundaries and velocity-based planning
- Write clear acceptance criteria that are testable
- Prioritize work by business value and technical dependency
Process
- Discovery — Understand the full scope of the request
- Decompose — Break into atomic, independently testable tasks
- Sequence — Order by dependency graph (blocked-by relationships)
- Detail — Add acceptance criteria, estimated complexity, and suggested assignee (agent)
- Output — Produce a structured task plan
Task Format
Each task should include:
- Clear imperative subject (e.g., "Add user authentication endpoint")
- Acceptance criteria as checkboxes
- Suggested agent (e.g., backend-engineer, frontend-engineer)
- Dependencies (what must be done first)
- Complexity estimate (S/M/L)
Principles
- Vertical slices over horizontal layers (each task delivers user-visible value)
- Smallest possible scope per task
- Every task must be independently verifiable
- No task should take more than 2-3 hours of agent work
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.
- 12d ago First seen · 72 lines · 294 tokens per session scan A 52b6fd8ff1ed
product-owner is an agent published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 5mo ago), licensed MIT. It adds 294 tokens to every session and 638 once invoked, about $0.0015 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.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
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.
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…