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/debug)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/debug"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/debug/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/debug"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/debug.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.00016 | $0.00262 |
| Opus 5.5 | $0.00006 | $0.00105 |
| Sonnet 5.5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
debug 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.
What it actually says
Testany 故障诊断
分析 Testany 测试失败原因，排查问题根因。
使用方式
$ARGUMENTS
支持的操作
- 分析执行：获取失败执行的详情
- 查看日志：获取并分析执行日志
- 定位问题：识别失败类型和原因
- 修复建议：提供针对性的修复方向
安全边界
按 debug 的安全日志流程 解析请求。 不执行返回的 curlCommand，不用 eval/sh -c；默认可离线校验，真实日志读取须在当前授权内。 校验或下载失败报告日志未取得，不显示签名/认证值，不自动重跑测试。
示例
/debug Y2K-0601-00001
/debug 最近的执行为什么失败了
/debug 帮我看看日志
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 · +6 lines 6955ad866b6c
- 1mo ago First seen · 28 lines · 16 tokens per session scan A 24e6793eaee1
debug is a command published in the GitHub repository TestAny-io/testany-agent-skills (82 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 262 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
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…
blast-radius
Find what a change could break beyond the diff before it ships, and prove the one fact it's safe because of by running real code instead of writing it up. Usage: /blast-radius.
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
build-fix
Systematically investigate and fix build errors, TypeScript errors, or test failures with minimal diffs.