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 sa-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/sa-playbook)<a href="https://agentmods.dev/skills/baodq97/open-plugin/sa-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/sa-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/sa-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/sa-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.00147 | $0.01709 |
| Opus 5.5 | $0.00059 | $0.00684 |
| Sonnet 5.5 | $0.00029 | $0.00342 |
| Haiku 4.5 | $0.00015 | $0.00171 |
Grade A, and why
sa-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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SA Playbook v1.0
Guides developers and tech leads through Solution Architecture tasks using the SFIA 9 framework. Combines a phase-based workflow with inline coaching to build SA competency from SFIA level 4 (Enable) toward level 5-6.
Core Principles
- Hybrid guidance — Walk through SA phases together, not just instruct. Recommend patterns, 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 (stakeholder maps, ADRs, C4 diagrams), not just checklists.
- YAGNI first — Always challenge: "Is this truly needed at the current scale?" Design for separation, deploy simply. Avoid over-engineering.
- SA does not own the roadmap — SA provides the dependency map and readiness milestones. Timeline decisions are made by the PO based on business priorities.
SA Workflow — 5 Phases
| # | Phase | Purpose | Key SFIA Skills | Key Artifacts |
|---|---|---|---|---|
| 1 | Discover | Understand context, stakeholders, constraints | BUSA, REQM | Stakeholder map, Context doc |
| 2 | Define | Formalize requirements, NFRs, boundaries | REQM, DATM, SCTY | Requirements doc, NFR matrix |
| 3 | Design | Create architecture, evaluate trade-offs | ARCH, DESN, NTDS, DBDS, DTAN | C4 diagrams, Component specs, Trade-offs |
| 4 | Decide | Validate decisions, get buy-in | TECH, CNSL, ARCH | ADRs, Risk assessment |
| 5 | Deliver | Document, communicate, handoff | ARCH, METL | Architecture doc, Dependency map, Milestones, Presentation |
For detailed phase activities, coaching prompts, and artifact guidance, consult references/sa-phases.md.
Session Management
Starting a Session
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 · 177 lines · 147 tokens per session scan A 05dd1b64b130
sa-playbook is a skill published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 147 tokens to every session and 1,709 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
customer-journey-map
Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.
visual-explainer
Generate self-contained HTML pages that visually explain technical material — systems, code changes, plans, data. Use when the user asks for any diagram or visual explanation, when they want a slide deck or a longform document (user guide, how-to, reference page), when another skill needs one rendered, or proactively…
verifying-design-canvas
Verify a live deployed app matches its Claude Design canvas (.dc.html): theme tokens, DOM/a11y structure, every interactive state — not just default view. Building instead of verifying? See artifact-design.
brand
A project-specific visual identity for chat cards and saved reports, using the project's colors, logo, and fonts. It finds these details in the repository or asks the user for them, then stores the result in a committable `.readable/` folder.
auditing-website-accessibility
Audits website accessibility for WCAG 2.2 AA compliance, generating findings and code fixes. Use when reviewing accessibility, keyboard navigation, screen reader compatibility, or inclusive design.
auditing-website-usability
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.