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/case-writing)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/case-writing"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/case-writing/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/case-writing"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/case-writing.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.00026 | $0.00407 |
| Opus 5 | $0.00013 | $0.00204 |
| Sonnet 5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
case-writing 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 9d 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
Testany Platform Case 编写
将传统测试场景拆解为 Testany platform cases，并生成可注册的 metadata、脚本和 ZIP 包。
使用方式
$ARGUMENTS
核心动作
- 场景拆解：先判断一个传统测试场景要拆成几个 Testany platform cases
- case package 生成：为每个 platform case 生成 metadata、脚本和 ZIP
- automation design 输出：明确后续是否需要
testany-pipeline - 上游优先级：优先读取 approved Test Spec 中的
Testany Automation Handoff
支持的 Executor
- PyRes (Python) - 推荐，适合 API 测试
- Postman - 无需编程，快速 API 验证
- Playwright - UI/E2E 测试
- Maven/Gradle - Java 项目测试
示例
/case-writing 写一个测试用户登录 API 的 Python 测试
/case-writing 生成 Playwright E2E 测试，测试购物车结算流程
/case-writing 创建 Postman Collection 测试支付接口
/case-writing 写一个 Java 测试，验证订单创建 API
/case-writing 根据 approved test spec 里的 Testany Automation Handoff 生成可上传到 Testany 的多个 cases
输出
- platform case inventory
- Testany-compatible 测试脚本
- 可直接上传的 ZIP 包
- 面向
testany-pipeline的 decomposition / handoff 摘要
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.
- 9d ago First seen · 44 lines · 26 tokens per session scan A 702dd7416531
case-writing is a command published in the GitHub repository TestAny-io/testany-agent-skills (81 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 407 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
playwright-test-heal
Run all my tests and fix the failing ones.
paul:verify
Guide manual user acceptance testing of recently built features.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.