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 jakesterns/agent-skills --skill test-strategygit clone --depth 1 https://github.com/jakesterns/agent-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/jakesterns/agent-skills/test-strategy)<a href="https://agentmods.dev/skills/jakesterns/agent-skills/test-strategy"><img src="https://agentmods.dev/badge/skills/jakesterns/agent-skills/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.1 | $0.00038 | $0.00315 |
| Opus 5 | $0.00019 | $0.00158 |
| Sonnet 5 | $0.00008 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
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 6d 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.
What it actually says
Test Strategy
Use this skill when a user asks what to test, how much to test, or how to validate a change before release.
Inputs
- Feature, bug fix, refactor, pull request, or release scope
- Existing test framework and commands
- Known risks, production incidents, or edge cases
Steps
- Identify behaviors that must remain true, not just lines of code that changed.
- Map risks to test levels: unit for pure logic, integration for contracts and data flow, end-to-end for critical user journeys, regression tests for bugs.
- Prioritize tests by impact, likelihood, and cost to maintain.
- Include negative cases, boundary cases, permissions, failure modes, and compatibility cases.
- Recommend test data and mocks only where they preserve realism.
- Define the smallest useful test suite for this change and the broader suite for release confidence.
- Provide commands to run if they can be inferred from the repo.
Output
Return:
- Risk-based test matrix
- Recommended new or updated tests
- Existing tests to run
- Gaps that require manual QA or instrumentation
- Confidence assessment
Guidelines
- Avoid blanket "add more tests" advice.
- Prefer tests that fail for the right reason.
- Keep tests aligned with user-visible behavior and stable contracts.
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.
- 6d ago First seen · 41 lines · 38 tokens per session scan A 3295689527c9
test-strategy is a skill published in the GitHub repository jakesterns/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 315 once invoked, about $0.0002 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.