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 agentmods add commands/testany-io/testany-agent-skills/casegit 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)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/case"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/case.svg" alt="Measured on agentmods" 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.00017 | $0.00767 |
| Opus 5 | $0.00009 | $0.00383 |
| Sonnet 5 | $0.00003 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
case 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 6d 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 case package 注册到平台，并管理 metadata、脚本和生命周期。
使用方式
$ARGUMENTS
核心动作
- 注册 case package：创建 shell case，补齐 metadata，并上传 ZIP
- 更新配置：修改 case metadata、可见性、labels、运行配置
- 上传脚本：上传或更新测试脚本 ZIP 包
- 查看用例：获取 case 详情和脚本
- 管理标签：为 case 添加分类标签
- dry run 验证：验证 case 是否 ready
示例
/case 把这些 ZIP 和 metadata 注册成 Testany cases
/case 更新 A1B2C3D4 的环境变量
/case 上传脚本到 A1B2C3D4
/case dry run A1B2C3D4
/case 给 A1B2C3D4 添加 regression 标签
重要边界
case是 Testany 平台上的原子自动化步骤包- 如果你只有传统测试场景，还没有拆解结果和脚本，请先用
/case-writing - Testany 不支持直接执行单条 case
- 如果要真正执行，注册完 case 后还需要
/pipeline
Case Labels (用例标签)
case_labels 用于对测试用例进行分类和过滤。重要：标签必须在系统中预先存在才能使用。
获取可用标签
在为用例设置标签前，先调用 testany_list_labels 获取系统中已有的标签列表：
testany_list_labels
testany_list_labels keyword="regression" # 按关键字过滤
创建新标签
如果需要的标签不存在，先调用 testany_create_label 创建：
testany_create_label name="my-new-label"
标签命名规则：
- 长度 1-255 字符
- 不能包含特殊字符：
",%,/,\,* - 不能使用保留名称：
root,testcaselibrary,test case library
为用例设置标签
创建或更新用例时，使用 case_labels 字段指定标签（必须是已存在的标签）：
testany_update_case key="A1B2C3D4" case_labels=["regression", "api-test"]
testany_bulk_update_cases keys=["A1B2C3D4", "B2C3D4E5"] case_labels=["smoke"]
testany_bulk_append_cases keys=["A1B2C3D4"] case_labels=["nightly"] # 追加标签
常见工作流
-
添加新标签到用例：
- 先
testany_list_labels检查标签是否存在 - 如不存在，
testany_create_label创建 - 最后
testany_update_case或testany_bulk_append_cases设置标签
- 先
-
批量更新标签：
testany_bulk_update_cases会替换所有标签testany_bulk_append_cases会追加新标签到现有标签
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.
- 6d ago First seen · 86 lines · 17 tokens per session scan A 80059edec3b4
case is a command published in the GitHub repository TestAny-io/testany-agent-skills (80 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 767 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.