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/cookys/autopilot/test-strategynpx skills add cookys/autopilot --skill test-strategygit clone --depth 1 https://github.com/cookys/autopilotWrote 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/cookys/autopilot/test-strategy)<a href="https://agentmods.dev/skills/cookys/autopilot/test-strategy"><img src="https://agentmods.dev/badge/skills/cookys/autopilot/test-strategy.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 | $0.00000 | $0.01048 |
| Opus 5 | $0.00000 | $0.00524 |
| Sonnet 5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade B, and why
test-strategy scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
!`cat .claude/test-strategy-config.md 2>/dev/null || echo "No project-specific test config found. Using generic defaults."` How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Strategy
Routing overlap? If this intent better matches a sibling skill, redirect per references/routing-tiebreaks.md (prefer test design over single-bug diagnosis).
Coexistence with Superpowers
This skill is autopilot's standalone fallback for testing methodology. If the superpowers plugin is installed, superpowers:test-driven-development is available — note these are NOT equivalent.
Differences worth knowing:
- TDD ≠ test-strategy.
superpowers:test-driven-developmentfocuses on the「先寫測試再寫實作」red-green-refactor cycle. autopilot:test-strategy covers test pyramid, baseline 守則, failure investigation funnel — orthogonal scope. - If you want both, use them together: TDD as the coding loop, test-strategy as the strategy frame.
.claude/dispatch-config.md's## Testing methodologychain controls orchestrator preference. - Standalone limitation (be honest about it). When
superpowersis NOT installed, the red-green-refactor coding loop has no native autopilot equivalent — this skill is the strategy frame, not a TDD substitute. For TDD specifically, installsuperpowers(test-driven-development) or run the red-green cycle manually. (autopilot deliberately does not ship atddskill: that loop is superpowers' lane, and duplicating it would violate the skill-proliferation discipline.)
!cat .claude/test-strategy-config.md 2>/dev/null || echo "No project-specific test config found. Using generic defaults."
Test Pyramid
Unit (frequent, per build) > E2E (per feature) > Stress (pre-release, rare)
Test Categories
| Type | Purpose | When | Scope |
|---|---|---|---|
| Unit | Logic correctness | Every build | Single function/class |
| E2E | System integration | Per feature / nightly | Full stack |
| Stress | Capacity limits | Before release | System under load |
| Regression | No breakage | Every PR | Affected modules |
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.
- 4d ago First seen · 103 lines · 0 tokens per session scan B ab21d8631f0e
test-strategy is a skill published in the GitHub repository cookys/autopilot (11 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,048 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…