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-spec-writer)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/test-spec-writer"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/test-spec-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-spec-writer"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/test-spec-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.00040 | $0.00490 |
| Opus 5 | $0.00020 | $0.00245 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
test-spec-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 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.
What it actually says
Test Spec Writer
启动测试规格与测试用例包撰写流程。基于批准的 Test Strategy 与 LLD 等基线，输出独立测试范围内完整、详细、可执行的 test case package。
使用方式
提供上游文档路径：
$ARGUMENTS
在研发流程中的位置
LLD → [Test Spec Writer] → Test Case Package → Test Reviewer
输出范围
test-spec-profile-v1的TRACEABILITY-METADATAblock- 追溯矩阵
- 覆盖率摘要
- 测试矩阵
- 详细测试用例
- 环境、数据、依赖与证据要求
- 开发内建验证前置条件
- 回归包、Smoke 包、自动化建议
Testany Automation Handoff（供testany-bot/case-writing消费）
核心原则
- Package 优先：输出完整测试包，而非零散 case
- Strategy 承接：只细化批准策略，不重写方法论
- 追溯强制：需求、接口、风险必须能映射到测试项
- 执行就绪：每个 case 都要可执行、可判定
- 边界清晰：不展开 unit、code-level integration、provider-side contract 的详细 case
- 覆盖率分项统计：按需求/风险/外部行为/场景/NFR 分项输出
- 脚本自检：写完后先跑
trace-lint，再用trace-build-rtm联合 PRD/Test Strategy 检查全局 RTM
请提供 PRD、API Contract、HLD、LLD、Test Strategy 路径开始撰写。
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 · 45 lines · 40 tokens per session scan A 7356b93dbfa5
test-spec-writer is a command published in the GitHub repository TestAny-io/testany-agent-skills (81 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 490 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-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.