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 testing-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/testing-playbook)<a href="https://agentmods.dev/skills/baodq97/open-plugin/testing-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/testing-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/testing-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/testing-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.00131 | $0.01670 |
| Opus 5.5 | $0.00052 | $0.00668 |
| Sonnet 5.5 | $0.00026 | $0.00334 |
| Haiku 4.5 | $0.00013 | $0.00167 |
Grade A, and why
testing-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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Playbook v1.0
Guides developers and QA through Testing tasks using the SFIA 9 framework. Combines a phase-based workflow with inline coaching to build testing competency from SFIA level 4 (Enable) toward level 5-6.
Core Principles
- Hybrid guidance — Walk through testing 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 (test strategies, test plans, defect reports), not just checklists.
- Risk-based testing — Prioritize testing by risk and impact, not by coverage metrics alone.
- Testing does not own the release decision — Testing provides risk assessment, release decision is made by delivery/product.
Testing Workflow — 5 Phases
| # | Phase | Purpose | Key SFIA Skills | Key Artifacts |
|---|---|---|---|---|
| 1 | Discover | Understand test context, requirements, stakeholders, risks | BUSA, REQM, TEST | Test context doc, Risk assessment, Stakeholder map |
| 2 | Plan | Design test strategy, select approaches, plan resources | TEST, QUAS, METL | Test strategy, Test plan, Environment requirements |
| 3 | Execute | Create and run tests, report defects | TEST, BPTS, PENT | Test cases, Test scripts, Defect reports, Test execution log |
| 4 | Evaluate | Analyze results, assess quality, determine readiness | QUAS, BURM, MEAS | Test summary report, Quality assessment, Risk report, Release recommendation |
| 5 | Improve | Retrospective, optimize processes, share learnings | METL, QUAS, BPRE | Test retrospective, Process improvement plan, Lessons learned |
For detailed phase activities, coaching prompts, and artifact guidance, consult references/testing-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.
- 1mo ago First seen · 172 lines · 131 tokens per session scan A 8045f3e2a4f9
testing-playbook is a skill published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 131 tokens to every session and 1,670 once invoked, about $0.0005 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
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.
test-scenarios
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
dotnet-test
This skill should be used when running .NET tests selectively with a build-first, test-targeted workflow. Use it for running tests with xUnit focus.
dotnet-verify
This skill should be used when working with Verify snapshot tests in .NET projects. Use when updating verified snapshots after intentional code changes, accepting new snapshots, discovering verify tests, or troubleshooting snapshot mismatches. Trigger phrases include "verify tests", "update snapshots", "accept…
go-tdd
Implement a Go feature using TDD methodology with up-to-date library documentation from Context7.
go-blackbox
Detect white box Go tests and propose conversion to black box tests (package footest), creating exporttest.go bridges when tests need access to internals.