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 cosmicstack-labs/mercury-agent-skills --skill test-strategygit clone --depth 1 https://github.com/cosmicstack-labs/mercury-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/cosmicstack-labs/mercury-agent-skills/test-strategy)<a href="https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/test-strategy"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-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/cosmicstack-labs/mercury-agent-skills/test-strategy"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/test-strategy.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.00021 | $0.00441 |
| Opus 5 | $0.00010 | $0.00220 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
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 8d 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
Design comprehensive test strategies that catch bugs early and scale with your product.
The Modern Test Pyramid
E2E (5%)
Integration (15%)
Component/Contract (30%)
Unit Tests (50%)
Layer Details
| Layer | Scope | Speed | Who Owns |
|---|---|---|---|
| Unit | Single function/class | ms | Developers |
| Component | UI component/module | ms-s | Developers |
| Contract | API boundaries | s | Dev + QA |
| Integration | Service interactions | s-min | QA |
| E2E | Full user flows | min | QA + DevOps |
Risk-Based Testing
- Identify risks for each feature (data loss, security, UX, performance)
- Score likelihood × impact
- Allocate test effort proportionally to risk score
- Reassess after each release
Coverage Goals
| Type | Target |
|---|---|
| Line coverage | >80% |
| Branch coverage | >75% |
| Mutation score | >60% |
| Critical path E2E | 100% |
| API endpoint tested | >90% |
Test Planning Template
## Feature: [Name]
- Unit tests: [count] — [files/scope]
- Integration tests: [count] — [services involved]
- E2E tests: [count] — [critical paths]
- Edge cases: [list]
- Performance threshold: [metric]
CI Integration
- Unit/component tests on every PR (fail under 5 min)
- Integration suite on every merge to main
- E2E nightly or on demand
- Flaky test detection → auto-quarantine → alert
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.
- 8d ago First seen · 66 lines · 21 tokens per session scan A f49153d7e48e
test-strategy is a skill published in the GitHub repository cosmicstack-labs/mercury-agent-skills (471 stars, last pushed 17d ago), licensed MIT. It adds 21 tokens to every session and 441 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
xdto-validate
A validator for XDTO packages in 1C:Enterprise. It checks the package model, its metadata object, and its connection to the configuration.