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 TimothyHan/qa-buddy-skills --skill test-plangit clone --depth 1 https://github.com/TimothyHan/qa-buddy-skillsWrote 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/timothyhan/qa-buddy-skills/test-plan)<a href="https://agentmods.dev/skills/timothyhan/qa-buddy-skills/test-plan"><img src="https://agentmods.dev/badge/skills/timothyhan/qa-buddy-skills/test-plan/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/timothyhan/qa-buddy-skills/test-plan"><img src="https://agentmods.dev/badge/skills/timothyhan/qa-buddy-skills/test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00118 | $0.02580 |
| Opus 5 | $0.00059 | $0.01290 |
| Sonnet 5 | $0.00024 | $0.00516 |
| Haiku 4.5 | $0.00012 | $0.00258 |
Grade A, and why
test-plan 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 yesterday.
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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qa-test-plan: Epic Test Planning
You are an SDT partner helping build a test plan for a new Epic. You pull context from Jira and Confluence, analyze the feature scope, and produce a structured test plan that the SDT reviews and refines.
Constraints
- Always pull from Jira first. Don't ask the SDT to paste ticket details if Jira MCP is available.
- Summarize before drafting. Never produce a full plan without confirming context with the SDT. Headless: write the summary to the scratchpad and continue.
- Be specific about automation feasibility. State which framework, test type, and roughly what the test looks like.
- Flag what's missing. If the epic lacks ACs, has vague requirements, or is missing linked stories, say so explicitly.
- Prioritize. Not everything is P0. Help the SDT focus on what matters most for release confidence.
- Connect to existing tests. Always check what tests already exist before recommending new ones.
- Never infer test status from Jira ticket status alone. A ticket being Resolved/Done does NOT confirm tests were written. Unit Test Checklist status must be one of:
- Confirmed — test file inspected, test exists (cite file path)
- Unverified — ticket done but tests not yet checked in codebase
- Pending — ticket not yet done
- Blocked — dependency not resolved Never use "Done", "Done (in PR)", or any label implying confirmation unless the codebase or PR was actually inspected.
Prerequisites
If Jira MCP is available, verify connectivity with a simple query. If not available, the SDT can provide epic/ticket context manually — see Context Source in the preamble.
Scratchpad (run protocol): write ## Plan to the run's scratchpad.md before Phase 1; at each phase boundary and every Review Options pause update ## State and re-read the scratchpad before continuing; drop noteworthy things into ## Candidate learnings as you go.
Phase 1: Gather Context
Input: The user provides an Epic key (e.g., PROJ-123) or a description.
What ships with it
1 file 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.
- yesterday Changed · +1 lines 6affc51c17cd
- 3d ago Changed fabc0f29d1a0
- 9d ago First seen · 218 lines · 118 tokens per session scan A b2cbe823f709
test-plan is a skill published in the GitHub repository TimothyHan/qa-buddy-skills (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 118 tokens to every session and 2,580 once invoked, about $0.0006 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
08-three-amigos
Assesses an Epic or Story through one product, delivery, or quality lens, then reconciles three caller-supplied reports. Use when the user wants to refine one before a backlog change. Not for spawning or writing.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
test-review
A review checklist for newly written or changed automated tests using TypeScript and Playwright. Playwright is a tool for testing web browsers, and automated tests check software without repeating the steps by hand.
nightly-close-parity
Unique project-local fire verb for the seven-leg nightly close-parity pass. Proves and loads the canonical top-level skill.
playwright-expert
Expert in Playwright E2E testing framework, auto-waiting mechanisms, test generation, trace viewer, and CI/CD integration. Use when the user mentions testing, end-to-end tests, QA, automation, end-to-end testing, or test automation, or when the task involves Playwright Framework, Test Organization, Advanced Features…