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 agentmods add skills/baodq97/open-plugin/pm-playbooknpx 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.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 | $0.00144 | $0.01796 |
| Opus 5 | $0.00072 | $0.00898 |
| Sonnet 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 4d 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.
- 4d 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 3mo ago), licensed MIT. It adds 144 tokens to every session and 1,796 once invoked, about $0.0007 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
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.