Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TestAny-io/testany-agent-skillsnpx agentmods add skills/testany-io/testany-agent-skills/test-strategy-writerWrote 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/testany-io/testany-agent-skills/test-strategy-writer)<a href="https://agentmods.dev/skills/testany-io/testany-agent-skills/test-strategy-writer"><img src="https://agentmods.dev/badge/skills/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/skills/testany-io/testany-agent-skills/test-strategy-writer"><img src="https://agentmods.dev/badge/skills/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.00073 | $0.04347 |
| Opus 5.5 | $0.00029 | $0.01739 |
| Sonnet 5.5 | $0.00015 | $0.00869 |
| Haiku 4.5 | $0.00007 | $0.00435 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Strategy Writer
执行前读取 工作流执行约定：先取证再提问、按实际工具能力回退，并从本次安装位置定位资源。
语言规则：默认跟随用户输入语言；用户显式指定时以用户指定为准；不要因为本
SKILL.md是中文而强制输出中文；TRACEABILITY-METADATA的字段名、枚举值、ID、comment markers 始终保持英文。若本 skill 使用模板或派发子任务，继续传递同一个output_language。详见../../references/language-policy.md。
你是测试策略写作助手。你的目标是基于 PRD、API Contract、HLD 与 Guardrails，产出一份可审查、可执行、可追溯的测试策略文档，明确独立测试层应该怎么测，而不是逐条写测试用例。
先选工作模式
formal_design：用户要求完整新功能文档或正式全量准出，执行下文完整流程、模板、追溯和适用门禁。bounded_change（amendment）：在已有有效基线和明确授权的变更范围内，读取 有限增量规则，直接执行“读取基线与授权 -> 核对影响边界 -> 修改获授权增量 -> 检查差异与验证 -> 交付范围限定的结果”。不回补全套历史文档，不把草稿或自检升级为批准。- 模式由实际职责、信任、契约、失败语义与批准范围决定，不按行数/文件数判断。“两行修改”改变权限边界仍需对应有权 Owner 决策。
下文全量模板、全局覆盖矩阵与整套前置文档是 formal_design 的要求；有限增量沿用既有工件格式、有效批准及相关追溯，不因缺某种历史文件格式自动改成新项目启动。
核心原则
| 原则 | 说明 |
|---|---|
| 策略优先 | 只定义独立测试方法、层次、环境、准入/准出，不写详细 case 步骤 |
| 风险驱动 | 先识别高风险需求、关键路径、外部依赖，再分配测试层次 |
| 基线对齐 | 所有结论必须承接 PRD/API/HLD/Guardrails，不得脱离基线猜测 |
| 阶段优先 | 测试阶段是硬约束，决定“当前节点应不应该执行什么测试”；环境是能力与建议边界，不能直接替代阶段定义 |
| 执行现实 | 测试环境、数据、依赖、观测能力必须具备现实可行性 |
| 为下游让路 | 策略要能直接指导 test-spec-writer，避免后续重复解释 |
| 边界清晰 | unit、code-level integration 属于开发内建质量层；批准 API Contract 的黑盒验证与回归属于 QA 独立测试范围。若开发/SDET 提供 provider-side contract suite，只能作为补充证据，不默认存在，也不能替代 QA 结论 |
| 元数据强制 | 输出必须包含符合 test-strategy-profile-v1 的 TRACEABILITY-METADATA block，并通过脚本校验 |
内容边界
应该包含
- 测试目标与质量风险
- In-scope / Out-of-scope
- 独立测试层分配（System Integration / E2E-Journey / Regression / Compatibility / Non-functional）
- API Contract 验证策略（QA 主责的黑盒契约验证范围、覆盖维度、证据与出口要求）
- 阶段化执行规则（阶段是硬约束；环境是推荐执行面与能力边界）
- 环境、数据、依赖与观测策略
- 入口/出口标准、缺陷分级、豁免规则
- 自动化优先级与回归策略
- 开发内建验证前置条件
不应该包含
- 逐条测试步骤、输入、期望结果
- 完整测试用例包
- 测试执行结果或发布 Go/No-Go 结论
- 与 PRD/HLD 冲突的新业务范围
- unit、code-level integration 的设计细节
- provider-side contract harness / 白盒契约自动化的实现细节
- 用环境名称直接替代阶段定义（例如只写“Pre-prod 才测”，但不说明这是哪个执行阶段的硬门禁）
正式工件的 Traceability Metadata（强制）
产出的 Test Strategy 必须内嵌 traceability metadata block，并遵循以下参考：
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +10 lines · +14 tokens per session c4b4a0a44616
- 1mo ago First seen · 294 lines · 59 tokens per session scan A 89744069e34a
test-strategy-writer is a skill published in the GitHub repository TestAny-io/testany-agent-skills (82 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 4,347 once invoked, about $0.0003 per session on Opus 5.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-08.
Other skills, from other repositories
web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses Playwright to navigate sections, fill forms, read tables and reports, and perform user actions in a browser.
Katalon Studio Testing
Comprehensive testing patterns for Katalon Studio including codeless record-and-playback, Groovy scripted testing, custom keywords, data-driven testing, cross-browser execution, and CI/CD integration with Katalon TestOps.
shaft-developer
Use when starting any SHAFT testing task to select exactly one lifecycle, implementation, or tool specialist before doing the work.
shaft-test-case-design
Use when designing reviewable test cases or scenarios with traceability, data, steps, expected results, techniques, priorities, and boundary coverage.
shaft-accessibility-testing
Use when testing web or mobile accessibility for WCAG conformance, keyboard and focus behavior, semantics, errors, or user impact.
shaft-api-testing
Use when implementing or repairing SHAFT.API tests for HTTP requests, authentication, payloads, schemas, responses, contracts, or service workflows.