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 pm-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/pm-playbook)<a href="https://agentmods.dev/skills/baodq97/open-plugin/pm-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/pm-playbook/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/baodq97/open-plugin/pm-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/pm-playbook.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.00144 | $0.01796 |
| Opus 5.5 | $0.00058 | $0.00718 |
| Sonnet 5.5 | $0.00029 | $0.00359 |
| Haiku 4.5 | $0.00014 | $0.00180 |
Grade A, and why
pm-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 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Playbook v1.0
Guides team leads and coordinators through Project Management tasks using the SFIA 9 framework. Combines a phase-based workflow with inline coaching to build project delivery competency from SFIA level 4 (Enable) toward level 5-6.
Core Principles
- Hybrid guidance -- Walk through PM phases together, not just instruct. Recommend approaches, 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 (project charters, RAID logs, status reports), not just checklists.
- Governance over control -- Establish governance frameworks, empower teams to execute within guardrails.
- PM does not own the technical solution -- PM provides constraints and governance, technical decisions are made by the engineering team.
PM Workflow -- 5 Phases
| # | Phase | Purpose | Key SFIA Skills | Key Artifacts |
|---|---|---|---|---|
| 1 | Discover | Understand project context, stakeholders, business case | PRMG, RLMT, INVA | Project brief, Stakeholder register, Business case summary |
| 2 | Define | Formalize scope, governance, success criteria | PRMG, PROF, BENM | Project charter, Governance framework, Benefits plan, RACI matrix |
| 3 | Plan | Create detailed plans, resource allocation, risk management | PRMG, DEMM, FMIT, MEAS | Project plan, Resource plan, Budget, Risk register (RAID), Communication plan |
| 4 | Execute | Monitor delivery, manage changes, report progress | PRMG, ISCO, CIPM, RLMT | Status reports, Change requests, Issue log, Milestone tracker |
| 5 | Close & Learn | Handover, benefits review, lessons learned | PRMG, BENM, MEAS, METL | Project closure report, Benefits realization report, Lessons learned, Handover document |
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.
- 1mo ago First seen · 181 lines · 144 tokens per session scan A 4a465950d2da
pm-playbook is a skill published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 144 tokens to every session and 1,796 once invoked, about $0.0006 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 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.
review-resume
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
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.
brainstorm-ideas-existing
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.