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 baodq97/open-plugin --skill po-playbookgit clone --depth 1 https://github.com/baodq97/open-pluginWrote 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/baodq97/open-plugin/po-playbook)<a href="https://agentmods.dev/skills/baodq97/open-plugin/po-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/po-playbook.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.00174 | $0.01793 |
| Opus 5 | $0.00087 | $0.00897 |
| Sonnet 5 | $0.00035 | $0.00359 |
| Haiku 4.5 | $0.00017 | $0.00179 |
Grade A, and why
po-playbook 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PO Playbook v1.0
Guides developers, product managers and aspiring POs through Product Owner tasks using the SFIA 9 framework. Combines a phase-based workflow with inline coaching to build PO competency from SFIA level 4 (Enable) toward level 5-6.
Core Principles
- Hybrid guidance — Walk through PO phases together, not just instruct. Recommend frameworks, draft artifacts collaboratively, and help complete the task.
- SFIA-mapped coaching — Every activity maps to a SFIA skill and level. Inline coaching explains what skill is being practiced and how to level up.
- Flexible phases — 5 phases provide structure, but skip or jump as context demands. No forced quality gates.
- Artifacts over theory — Each phase produces concrete deliverables (vision docs, roadmaps, backlogs), not just checklists.
- Outcome over output — Always challenge: "Does this feature deliver measurable user/business value?" Focus on outcomes, not feature count.
- PO does not own architecture — PO provides business priorities, timeline, and budget. Technical dependency decisions are made by the SA/engineering team.
PO Workflow — 5 Phases
| # | Phase | Purpose | Key SFIA Skills | Key Artifacts |
|---|---|---|---|---|
| 1 | Discover | Understand market, users, business context | BUSA, MRCH, URCH | Market analysis, User personas, Problem statement |
| 2 | Define | Formalize vision, strategy, success metrics | PROD, CEXP, FEAS | Product vision, Value proposition, Success metrics |
| 3 | Prioritize | Manage backlog, create roadmap, make trade-offs | PROD, REQM, DEMM | Product backlog, Roadmap, Prioritization matrix |
| 4 | Plan | Coordinate delivery, manage stakeholders, mitigate risk | DEMG, RLMT, BURM | Release plan, Stakeholder map, Risk register |
| 5 | Deliver & Learn | Launch, measure, iterate, improve | MEAS, BPRE, RELM | Launch checklist, Metrics dashboard, Retrospective |
For detailed phase activities, coaching prompts, and artifact guidance, consult references/po-phases.md.
What ships with it
6 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.
- 7d ago First seen · 179 lines · 174 tokens per session scan A ea27153883c6
po-playbook is a skill published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 174 tokens to every session and 1,793 once invoked, about $0.0009 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 skills, from other repositories
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
job-stories
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.
wwas
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.