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/pipeline)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/pipeline"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/pipeline/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/pipeline"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/pipeline.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.00035 | $0.00292 |
| Opus 5 | $0.00017 | $0.00146 |
| Sonnet 5 | $0.00007 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
pipeline 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 10d 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 测试流水线：创建执行与编排单元，组织 cases 的依赖、relay 和分支逻辑。
使用方式
$ARGUMENTS
支持的操作
- 创建流水线：优先根据上游 decomposition 组合多个 case 创建 pipeline
- 配置依赖：设置 whenPassed/whenFailed 执行条件
- 配置 Relay：设置用例间的变量传递
- 更新流水线：添加/移除 case，修改执行顺序
- 单 case 可执行化：即使只有一个 case，也创建一条 pipeline 作为执行入口
示例
/pipeline 把登录和查询用例组成流水线
/pipeline 配置 TOKEN 从 A1B2C3D4 传递到 E5F6A7B8
/pipeline 给 Y2K-0601 添加新用例
/pipeline 根据 case-writing 产出的 decomposition 创建订阅流程 pipeline
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.
- 10d ago First seen · 30 lines · 35 tokens per session scan A 518ea7a4bfc4
pipeline is a command published in the GitHub repository TestAny-io/testany-agent-skills (81 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 292 once invoked, about $0.0002 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
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
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…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.