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.
git clone --depth 1 https://github.com/TestAny-io/testany-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/commands/testany-io/testany-agent-skills/test-strategy-writer)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/test-strategy-writer"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/test-strategy-writer/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/commands/testany-io/testany-agent-skills/test-strategy-writer"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/test-strategy-writer.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.00027 | $0.00406 |
| Opus 5 | $0.00014 | $0.00203 |
| Sonnet 5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
test-strategy-writer 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 11d 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 Writer
启动测试策略撰写流程。基于 PRD、API Contract、HLD 与 Guardrails，产出可审查、可执行的独立测试策略。
使用方式
提供上游文档路径：
$ARGUMENTS
在研发流程中的位置
PRD → API Contract → HLD → [Test Strategy Writer] → Test Strategy → Test Strategy Reviewer → LLD
输出范围
test-strategy-profile-v1的TRACEABILITY-METADATAblock- 测试目标与质量风险
- In-scope / Out-of-scope
- 独立测试层分配
- 环境、数据、依赖与观测策略
- 入口/出口标准
- 自动化与回归策略
- 开发内建验证前置条件
核心原则
- 只写怎么测：不写详细 test case
- 风险驱动：高风险能力优先建模
- 基线对齐：承接 PRD/API/HLD/Guardrails
- 执行现实：环境和依赖必须可落地
- 边界清晰：不负责 unit、code-level integration、provider-side contract 的设计
- 脚本自检：写完后先跑
trace-lint，再用trace-build-rtm联合 PRD 检查追溯闭环
请提供 PRD、API Contract、HLD 路径开始撰写。Guardrails 如存在请一并提供。
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.
- 11d ago First seen · 43 lines · 27 tokens per session scan A 77f4684ab4ee
test-strategy-writer is a command published in the GitHub repository TestAny-io/testany-agent-skills (81 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 406 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-08-30.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.