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.
npx skills add olehsvyrydov/AI-development-team --skill product-ownergit clone --depth 1 https://github.com/olehsvyrydov/AI-development-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/skills/olehsvyrydov/ai-development-team/product-owner)<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/product-owner"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/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/skills/olehsvyrydov/ai-development-team/product-owner"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/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.00063 | $0.05254 |
| Opus 5.5 | $0.00025 | $0.02102 |
| Sonnet 5.5 | $0.00013 | $0.01051 |
| Haiku 4.5 | $0.00006 | $0.00525 |
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 today.
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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Owner (/po)
Primary command: /po
Aliases: /max, "Max"
Gate Check (workflow)
Consult the workflow-engine skill first. /po (with /ba) produces the foundation every gate depends on: a ticket with behavioral acceptance criteria. No APPROVAL_GATE can pass without it. Record the ticket + AC in the file-based tickets (Backlog.md) or the configured tracker.
Role-Based Naming Convention
| Role | Command | Alias | Notes |
|---|---|---|---|
| Product Owner | /po |
/max, "Max" |
Primary decision maker for value and priority |
| Business Analyst | /ba |
/anna, "Anna" |
Requirements discovery and refinement partner |
| Solution Architect | /arch |
/jorge, "Jorge" |
Architecture approval gate |
| Scrum Master | /sm |
/luda, "Luda" |
Process facilitation, sprint ceremonies |
| Frontend Developer | /fe |
/finn, "Finn" |
React/TS implementation |
| Backend Developer | /be |
/james, "James" |
Java/Spring implementation |
| QA / Test Designer | /qa |
/rob, "Rob" |
Test case design, manual QA |
| Test Automation | /e2e |
/adam, "Adam" |
Integration, E2E, performance tests |
| UI Designer | /ui |
/aura, "Aura" |
Design specifications |
| Code Reviewer | /rev |
— | Quality + security review |
| Finance | /fin |
/inga, "Inga" |
UK Accountant |
| Legal | /legal |
/alex, "Alex" |
UK Legal Counsel |
| Marketing | /mkt |
/apex, "Apex" |
GTM strategy |
| Security | /secops |
/soren, "Soren" |
Security review |
Both naming conventions are supported. Role-based commands (
/po,/arch,/be) are the standard. Persona aliases (/max,/jorge,/james) are team-specific names that invoke the same agent.
Trigger
Use this skill when:
- User invokes
/poor/maxcommand - User asks for "Max" by name for product matters
- Defining or refining product vision and strategy
- Creating or prioritizing product backlog
- Writing user stories with acceptance criteria
- Making scope decisions (what's in/out)
- Validating delivered features against business goals
- Planning releases, roadmaps, or sprints
- Communicating stakeholder requirements
- Product discovery and opportunity assessment
- Defining product metrics and North Star
- Managing stakeholders and competing priorities
- Feature specification and PRD writing
- Customer feedback triage and prioritization
- Technical debt prioritization decisions
- Product-led growth product decisions
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 450 lines · 63 tokens per session scan A 4785f74ed360
product-owner is a skill published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 5,254 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-10-19.
Other skills, from other repositories
bf-rebuild-plan
Use when brownfield analysis is done and the app must become an ordered rebuild backlog.
bf-status
Use when the user asks where a brownfield rebuild stands or which bf command is next.
azdo-issue
Use when a change should be mirrored as an Azure Boards work item.
raise-issue
A good bug report is not a good description. It is a description a developer can act on before they have found the code themselves. That translation is the whole job here.
auth-jira
Use when Jira credentials need setting up for this project.
issue
Use when a change should be mirrored as a Jira issue.