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 aks-builds/quality-skills --skill test-strategygit clone --depth 1 https://github.com/aks-builds/quality-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/aks-builds/quality-skills/test-strategy)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/test-strategy"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/test-strategy/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/aks-builds/quality-skills/test-strategy"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/test-strategy.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.00153 | $0.02548 |
| Opus 5 | $0.00077 | $0.01274 |
| Sonnet 5 | $0.00031 | $0.00510 |
| Haiku 4.5 | $0.00015 | $0.00255 |
Grade A, and why
test-strategy 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 10d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Strategy
You are an expert in designing test strategies — deciding what to test where, what to test how, and what not to test at all. Your goal is to help teams build a testing approach proportional to their risk, language stack, and constraints rather than a one-size-fits-all pyramid copied from a blog post. Don't fabricate strategy patterns or invented categorical bins. Anchor recommendations in well-known frameworks (test pyramid, testing trophy, risk-based testing) and in the specific context the user describes.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- Architecture — monolith, microservices, mobile app, embedded system, ML / data pipeline. Strategies differ.
- Team shape — engineer-owned tests, dedicated QA, hybrid. Determines authoring patterns.
- Existing pyramid — what's already in place, what's broken, what's missing.
- Compliance constraints — regulated industries (healthcare, finance, automotive) drive specific test categories.
- Release cadence — multi-deploy-per-day vs quarterly release. Affects how much can ride on E2E gates.
If the file does not exist, ask: architecture, deployment cadence, team makeup, what specific pain is prompting the strategy review.
The pyramid (and its critics)
Mike Cohn's pyramid says: many fast, focused unit tests at the base; fewer slower integration tests in the middle; very few expensive end-to-end tests at the top.
/\
/ \ End-to-End (few)
/----\
/ \ Integration (some)
/--------\
/ \ Unit (many)
/____________\
It's still a useful shape for most stacks. The critics (e.g., Kent C. Dodds with the "testing trophy") argue for more weight on integration in frontend / React projects:
_____
| | End-to-End
|-----|
| |
| | Integration
| |
|-----|
| | Unit
|---|
| | Static (types, lint)
-----
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.
- 10d ago First seen · 248 lines · 153 tokens per session scan A e09b63f280d8
test-strategy is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed today), licensed MIT. It adds 153 tokens to every session and 2,548 once invoked, about $0.0008 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
test-case-writer
Use when someone asks to generate test cases, write test cases from a user story, create test cases from a BRD, design test cases from a mockup or wireframe, or produce a test case table from requirements.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
test-strategy
A method for deciding how a feature should be tested by turning risks into testing scope, depth, and priorities. TDD, or test-driven development, is not the focus here; this works at the system level through UI, API, manual, and specialist testing.
regression-testing
A workflow for deciding which existing tests should run after a code change. Regression testing checks that a change has not broken features that already worked.
exploratory-testing
A method for exploratory testing, where a tester learns an unfamiliar system while looking for risks instead of following only predefined test cases. It produces structured notes about the system, risks, test ideas, bugs, and unanswered questions.