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/ba-playbooknpx skills add baodq97/open-plugin --skill ba-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/ba-playbook)<a href="https://agentmods.dev/skills/baodq97/open-plugin/ba-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/ba-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.00170 | $0.01773 |
| Opus 5 | $0.00085 | $0.00886 |
| Sonnet 5 | $0.00034 | $0.00355 |
| Haiku 4.5 | $0.00017 | $0.00177 |
Grade A, and why
ba-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 5d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BA Playbook v1.0
Guides developers, analysts and aspiring BAs through Business Analysis tasks using the SFIA 9 framework. Combines a phase-based workflow with inline coaching to build BA competency from SFIA level 4 (Enable) toward level 5-6.
Core Principles
- Hybrid guidance — Walk through BA phases together, not just instruct. Recommend techniques, 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 (requirements docs, process maps, data models), not just checklists.
- Root cause over symptoms — Always challenge: "Are we solving the right problem?" Investigate root causes before proposing solutions.
- BA does not own the solution — BA provides analysis, options, and recommendations. Solution decisions are made by stakeholders and the delivery team.
BA Workflow — 5 Phases
| # | Phase | Purpose | Key SFIA Skills | Key Artifacts |
|---|---|---|---|---|
| 1 | Discover | Investigate business situation, stakeholders, current state | BUSA, RLMT | Stakeholder map, Problem statement, As-is analysis |
| 2 | Define | Formalize requirements, scope, feasibility | REQM, FEAS, BSMO | Requirements doc, Business model, Feasibility assessment |
| 3 | Analyze | Improve processes, model data, analyze UX | BPRE, DTAN, UNAN | Process maps, Data model, UX analysis |
| 4 | Design | Select methods, design solution, define acceptance | METL, BPTS, STPL | Solution options, Acceptance criteria, Methods selection |
| 5 | Deliver & Validate | Test, handoff, manage change | BPTS, CNSL, CIPM | Test plan, Handoff package, Change impact assessment |
For detailed phase activities, coaching prompts, and artifact guidance, consult references/ba-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.
- 5d ago First seen · 180 lines · 170 tokens per session scan A dd37ba6f3cee
ba-playbook is a skill published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 170 tokens to every session and 1,773 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
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.
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.
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…
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.