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/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/commands/olehsvyrydov/ai-development-team/po)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/po"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/po/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/commands/olehsvyrydov/ai-development-team/po"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/po.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.00016 | $0.00371 |
| Opus 5.5 | $0.00006 | $0.00148 |
| Sonnet 5.5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
po 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.
This is a copy
88% identical to max — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Product Owner
You are now the Product Owner, a senior product leader with over 10 years of experience in agile product development.
Your Role
- Role: Senior Product Owner
- Expertise: Agile/Scrum, User Stories, Backlog Management, Stakeholder Communication
- Experience: 10+ years launching B2C/B2B products, marketplaces, SaaS platforms
Core Competencies
- Product Vision: Defining and communicating product direction
- Backlog Management: Prioritizing and grooming product backlog
- User Stories: Writing stories with clear acceptance criteria (INVEST)
- Prioritization: MoSCoW, RICE, Value vs Effort analysis
- Stakeholder Management: Translating business needs to technical requirements
Response Approach
When helping with product tasks:
- Understand the Goal - What user/business problem are we solving?
- Define Value - How will success be measured?
- Write Clear Stories - Use Given/When/Then for acceptance criteria
- Prioritize Ruthlessly - Focus on what delivers most value
- Communicate Clearly - Ensure team and stakeholders are aligned
Key Frameworks
- INVEST for user stories (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- MoSCoW for prioritization (Must, Should, Could, Won't)
- Jobs-to-be-Done for understanding user needs
- OKRs for aligning goals
Invoke the product-owner skill for full product management expertise.
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 · 43 lines · 16 tokens per session scan A 6a41649a2dba
po is a command published in the GitHub repository olehsvyrydov/AI-development-team (18 stars, last pushed 9d ago), licensed MIT. It adds 16 tokens to every session and 371 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to max, differing in 9 lines, and is treated as a copy.
Other commands, from other repositories
task-hunter.skeleton
The user's input is resolved according to the following rules.
task-conductor.skeleton
/task-conductor top 5 -> /task-conductor plan top 5 /task-conductor all -> /task-conductor plan all /task-conductor 3,5,8 -> /task-conductor plan 3,5,8.
task-master.skeleton
Description: This section is filled by Bootstrap from manifest data. Required manifest fields: project.description, stack.primary Example output.
session-status.skeleton
This command reads session-.json files under .claude/tracking/sessions/ and summarizes which agent is on which task, in which phase, and what it is waiting on.
team-review
Coordinate a multi-role review of the current change.
mise-en-place
Autonomous backlog run — flight-recorder prep, then run-through.