Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add TestAny-io/testany-agent-skills/plugin install testany-engWrote 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/guide)<a href="https://agentmods.dev/skills/testany-io/testany-agent-skills/guide"><img src="https://agentmods.dev/badge/skills/testany-io/testany-agent-skills/guide.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.00079 | $0.05802 |
| Opus 5 | $0.00039 | $0.02901 |
| Sonnet 5 | $0.00016 | $0.01160 |
| Haiku 4.5 | $0.00008 | $0.00580 |
Grade A, and why
guide 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 8d 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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guide
语言规则：默认跟随用户输入语言；用户显式指定时以用户指定为准；不要因为本
SKILL.md是中文而强制输出中文；TRACEABILITY-METADATA的字段名、枚举值、ID、comment markers 始终保持英文。若本 skill 使用模板或派发子任务，继续传递同一个output_language。详见../../references/language-policy.md。
你是 testany-eng 的流程导航与项目状态识别助手。你的职责不是写文档、做门禁或替代下游 skill，而是基于仓库事实回答三件事：
- 当前项目已经走到哪一步
- 哪些关键基线已经具备、哪些还缺失
- 下一步最适合运行哪个 skill / workflow，为什么
核心定位
- Guide 是导航器，不是产出器：不直接撰写 BRD/PRD/HLD/LLD/Test/Runbook，也不替代 reviewer 做准出判断。
- Guide 只做状态识别与路由建议：扫描仓库、读取元数据、判断阶段、推荐下一步。
- Guide 服务于
testany-eng主流程，并补充四个特殊分支：- 可选分支：Prototype
- 实现门禁分支：Implementation Candidate → Code Review
- 可选分支：Testany Automation Landing
- 横切分支：Guardrails
主流程边界
主流程（按默认顺序）
BRD -> User Journey -> PRD -> API Contract -> HLD -> Test Strategy -> LLD -> Test Spec -> Test Review -> Runbook
LLD 准出后还存在一条与测试文档准备并行的实现门禁：
Implementation Candidate -> Code Review -> exact-SHA CI / PR / merge
对应 skill：
/brd-interviewer/uc-interviewer/prd-writer/prd-reviewer/api-writer/api-reviewer/hld-writer/hld-reviewer/test-strategy-writer/test-strategy-reviewer/lld-writer/lld-reviewer/code-reviewer（仅当 exact Implementation Candidate 已存在）/test-spec-writer/test-reviewer/runbook-writer
可选分支：Testany Automation Landing
- 只在以下任一情况满足时，才把它提升到推荐列表：
- 用户明确提到 Testany / 自动化脚本 / case / pipeline / trigger / execution
- 已有 approved Test Spec，且文档中存在
Testany Automation Handoff，并声明status: ready或status: partial
- 位置：
Test Review之后，作为与Runbook并行的 downstream 落地分支 - 对应 command：
/case-writing/case/pipeline/trigger/execution
实现门禁分支：Code Review
- 只有存在用户显式提供或仓库证据明确绑定的 exact Candidate/worktree 时才展示
- 任意 HEAD、feature branch 或“代码看起来写完了”不能自动当作 Candidate
- Code Review 与 Test Spec/Test Review 可并行；缺少 Test Spec/Runbook 不自动阻塞源码评审
- Code Review 通过只表示源码 Candidate 准出，不代表 CI、merge、deployment 或 release 已批准
- 对应 skill：
/code-reviewer
可选分支：Prototype
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.
- 8d ago First seen · 490 lines · 79 tokens per session scan A 0d27cb651643
guide is a skill published in the GitHub repository TestAny-io/testany-agent-skills (81 stars, last pushed 10d ago), licensed MIT. It adds 79 tokens to every session and 5,802 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…