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/trigger)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/trigger"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/trigger/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/trigger"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/trigger.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.00024 | $0.00424 |
| Opus 5.5 | $0.00010 | $0.00170 |
| Sonnet 5.5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
trigger 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 Trigger
为已有 pipeline 配置执行入口，或立即发起一次执行。Trigger 是执行入口，不是编排层。
使用方式
$ARGUMENTS
按 整体目标交接：仅启动返回真实 key 即止；要求等终态则继续 execution 工作流，沿用等待预算，不重试或取消。
支持的操作
- 立即执行一次：Run Now，直接发起一次 pipeline execution
- 定时计划：创建 Plan，配置 cron 表达式
- 手动触发：配置 Manual Trigger（当前若 MCP 未提供 tools，则走 UI fallback）
- 事件触发：创建 Gatekeeper，接入 Jenkins/GitHub Actions 等外部系统
- 管理配置：更新或删除已有 trigger
示例
/trigger 立即执行 Y2K-0601
/trigger 给 Y2K-0601 创建 Gatekeeper
/trigger 每天凌晨 2 点执行回归测试
/trigger 给验收流水线创建一个 Manual Trigger
/trigger 接入 GitHub Actions
重要边界
- 如果你要“现在立刻跑一次”，用
/trigger - 如果执行已经发起，后续看进度、查历史、取消、失败交接，请用
/execution - 配置入口不自动授权执行；Manual Trigger 的 UI 指导要标明尚未配置，不替换其他类型
- 返回执行 key 只证明已发起，不证明成功；配置创建/更新后核对状态，读回失败标为部分完成/核验受阻
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 · +4 lines b7634eb64ed0
- 1mo ago First seen · 36 lines · 24 tokens per session scan A db3a46005aa2
trigger is a command published in the GitHub repository TestAny-io/testany-agent-skills (82 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 424 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
qa-sweep
Full platform QA sweep — auto-discovers every page, tests every UI element via browser automation, creates GitHub issues for all findings.
qa-e2e
End-to-End tests with Playwright or Cypress.
test-cloud-ui
Trigger the CI UI smoke test workflow with an optional custom test prompt.
review-before-deploy
Execute comprehensive pre-deployment review using code-review-agent with all relevant platform agents. Run complete deployment readiness checklist: verify all tests pass (unit, integration, E2E), security audit clean (no Critical/High issues), performance benchmarks met (Lighthouse > 90), TypeScript compilation…
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.