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 skills/backtocimacoppi/praxis/test-execution-routernpx skills add BackToCimaCoppi/Praxis --skill test-execution-routergit clone --depth 1 https://github.com/BackToCimaCoppi/PraxisWrote 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/backtocimacoppi/praxis/test-execution-router)<a href="https://agentmods.dev/skills/backtocimacoppi/praxis/test-execution-router"><img src="https://agentmods.dev/badge/skills/backtocimacoppi/praxis/test-execution-router.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.00102 | $0.03514 |
| Opus 5 | $0.00051 | $0.01757 |
| Sonnet 5 | $0.00020 | $0.00703 |
| Haiku 4.5 | $0.00010 | $0.00351 |
Grade A, and why
test-execution-router 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
测试执行路由
本 skill 只回答：冻结用例如何被准备、执行、路由和收口。不要在本层改用例口径；不要写项目凭据或平台专属细节。
0. 同一 goal 内的两种模式
| 模式 | 发生时点 | 可以做 | 禁止做 |
|---|---|---|---|
bootstrap M0 启动检查 |
goal 首个里程碑 | 实现/修复测试资产、runner、夹具、数据/环境适配与证据工具；每个命中面运行一个最小健康探针 | 改冻结用例语义、扩大用户授权、给逐 AC 提前签发 Ready |
verification 正式验证 |
goal 各施工切片内及候选交付前 | 跑冻结矩阵、封存 raw、派生证据状态；发现基础设施缺陷可就地修复并按影响面重跑 | 手填 VERIFIED、削弱断言、把产品现状反写测试 |
两种模式执行前都必须满足：
- 已读取冻结用例规格。
- 已确认
execution_ref或预定锚点。 - 已生成执行面矩阵：单元、接口、DB 预置、DB 终态、Web/admin UI、小程序 UI、视觉、手工；本任务命中面各一行，N/A 有可核理由。
- 已识别项目执行 skill；如果项目没有执行 skill，先报告缺口。
涉及真实动作时必须有上游用户授权锚点，逐项锁定目标环境、精确动作、目标对象、费用上限（含重试储备）与副作用范围。没有独立 readiness 门票；bootstrap 的失败先在 goal 内自愈。只有 goal-charter §4 白名单（真值矛盾 / 死亡线 / 未预授权动作，细则以彼处为真值）或计划内真实人工里程碑才交给用户；安全路径穷尽或达到限轮只交付 EXECUTION_BLOCKED，不前拉上游。
禁止行为：
- 边执行边修改断言。
- 用“环境不方便”跳过自动化。
- 把手工验证计作自动化覆盖。
- 把 AI 可控浏览器/开发者工具、DOM/data 断言、截图或 VLM 判读降级成手工。
- 失败后只写“测试失败”，不分类。
- 状态账本自证、派生聚合物冒充 raw、从账本反向改 raw、事后补绑候选版本或环境。
1. 执行流程
1.1 bootstrap M0 启动检查
- 读取冻结用例、执行面矩阵、上游授权与项目执行 skill；逐面加载对应参考。
- 先查项目正式测试基座、稳定 runner/夹具/环境适配与其登记索引，逐项记录
稳定路径 / 来源 commit / 当前分支是否可达 / 兼容性探针；可复用且可达的资产先复用，禁止无声重造。资产只存在于兄弟分支时标记PROPAGATION_REQUIRED，不得假称已经继承，也不得擅自合并分支。 - 每个命中面填写：环境身份/保真度、凭据位置、数据建立/清理/恢复、部署通路、预算、最小健康探针与人工边界；N/A 面填写证据化理由。
- 实现或修复
execution_ref、测试资产、runner、夹具、环境适配与证据工具；错误命令、路径和依赖属于本模式自愈项。 - 每个命中面只运行一个能区分“执行基础设施坏了”与“可以开始工作”的健康探针。报告状态仅为
HEALTHY / REPAIRED / BLOCKED_AUTH / MANUAL_BOUNDARY，不得逐 AC 预演或签发 Ready。 - 输出
_shared/T{n}-goal启动检查.md。这份报告是 goal 的首个运行记录，不是章程准入证明，也不冻结测试资产版本；资产继承清单是复用事实，不是新准入闸。
1.2 verification 正式验证
- 复验冻结用例、M0 启动检查、当前测试资产和候选 commit/tree。
- 按矩阵路由执行测试。发现测试资产/runner/夹具/环境适配/证据工具缺陷时，在同一 goal 内修复；登记影响面，重跑受影响测试和证据。
- 编号覆盖核对：冻结
assertion_index的每个AC-x都在测试资产里有字面落点；项目检查器必须通过。 - 每次运行按 §3.5 单向封存证据，再派生
VERIFIED / BLOCKED / MISSING / WAIVED。 - 运行项目执行证据检查器；失败按 §4 分类并路由，产出执行报告。
2. 路由表
| 用例类型 | 路由 |
|---|---|
| 单元测试 | 项目执行 skill 的 unit 参考 |
| 接口测试 | 项目执行 skill 的 api 参考 |
| DB 预置/校验 | 项目执行 skill 的 db 参考 |
| Web UI 自动化 | 项目执行 skill 的 web-ui 参考 |
| 小程序 UI 自动化 | 项目执行 skill 的 mp-ui 参考 |
| 视觉/VLM 验收 | 项目执行 skill 的 visual 参考 |
| 交付/发布验证 | 项目执行 skill 的 release/evidence 参考 |
| 手工验证 | 项目执行 skill 的 evidence 参考；只生成 runbook 与回传要求 |
What ships with it
2 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.
- 6d ago First seen · 178 lines · 102 tokens per session scan A aef1d3ad2c4e
test-execution-router is a skill published in the GitHub repository BackToCimaCoppi/Praxis (6 stars, last pushed 12d ago), licensed Apache-2.0. It adds 102 tokens to every session and 3,514 once invoked, about $0.0005 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-31.
Other skills, from other repositories
wincreator
Proves that agent work is actually done: each claim becomes a ledger row with a gate that was executed, captured raw evidence, and a status a builder is not allowed to write for itself. Use when a technical result must be auditable later — shipping or migrating something users depend on, a change whose failure is…
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.