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 skills add it235/multica-best-practices --skill multica-test-orchestrationgit clone --depth 1 https://github.com/it235/multica-best-practicesWrote 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/it235/multica-best-practices/multica-test-orchestration)<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-test-orchestration"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-test-orchestration/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/skills/it235/multica-best-practices/multica-test-orchestration"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-test-orchestration.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.00053 | $0.02338 |
| Opus 5 | $0.00026 | $0.01169 |
| Sonnet 5 | $0.00011 | $0.00468 |
| Haiku 4.5 | $0.00005 | $0.00234 |
Grade A, and why
multica-test-orchestration 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 2d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Orchestration（验收标准验证者 · 编排）
你对「需求到底实现没有」负责。测试左移，分 T1 / T2 / T3。T3 必须等待 DevOps G2.5 PASS 后再执行自动化。
本 skill 不属于 T1/T2/T3 任一阶段，是跨阶段编排入口：路由、评论拼接、BLOCKED、T3 合并裁决。整合自
acceptance-verifier-squad；方法细节在各-t1/-t2/-t3子 skill。
Platform 协作
| Platform skill | 本 skill 用途 |
|---|---|
multica-platform-jira |
T2/T3 前读 Issue 全评论（get-issue / 等价） |
团队知识库（可选） |
T1 Step 0（经 multica-test-t1-design） |
multica-platform-apifox |
T1 并行场景 + T3 跑批（经 t1-design / t3-api-automation） |
T1 采集（JIRA / Confluence / Figma）经 multica-test-t1-design → platform-jira / confluence / figma。凭据与 CLI 只查 platform skill。
子 skill 路由（必须 Read 后再做）
| 阶段 | Skill | 产出 |
|---|---|---|
| 编排/门禁 | 本文件 | 阶段卡、BLOCKED 原因 |
| T1 测试设计 | multica-test-t1-design |
Confluence 用例全文 + Apifox 场景 + e2e 规划 |
| T1 质检 | multica-review-test |
审 Confluence；👤 口令后 XMind/JIRA |
| 并行接口场景 | multica-platform-apifox |
按 API 契约补场景（AI 分支） |
| T2 | multica-test-t2-coverage |
Confluence 增量 + Apifox + MULTICA §2 e2e 入库 |
| T3 接口 | multica-test-t3-api-automation → multica-platform-apifox |
Apifox 日志 + 参与总报告 |
| T3 UI | multica-test-t3-ui-automation |
pytest+Playwright 1:1 执行 |
| T3 裁决 | 编排合并两侧证据 | 唯一 PASS/FAIL/BLOCKED |
智能体可复制指令见 references/agent-instructions.md。
Skill 交叉引用见 references/skill-inventory.md；T3 合并报告见 references/t3-merge-report.md；自动化入仓见 references/automation-assets-lifecycle.md。
任务卡（缺则停止）
stage: T1 | T2 | T3 | parallel-api
issue: # Multica 与/或 Jira Key
ac_source: # Issue/PRD 带编号 AC- 原文位置
T2 / T3 材料：只从本 Issue 描述 + 全部评论（含附件名）拼接。拼不齐 → 中断，输出缺失名单，等人类在评论补齐后再继续。禁止臆造，禁止用本机 mock / 未在评论出现的 URL 顶替。
从评论拼接（强制）
进入 T2 / T3 / parallel-api 前，必须 jira_cli.py get-issue --comments（或等价读全评论），按下面识别并填任务卡。
| 字段 | 评论里出现任一即可 |
|---|---|
g2_pass |
Leader 明确写 G2 PASS / G2 汇合判门 PASS |
g2_sha / 变更 |
合入 SHA、前后端 commit、变更文件表、或 MR/PR 链接 |
api_contract |
Apifox/OAS 链接，或明文 N/A + 复用哪条接口/链路 |
g25_pass |
Leader/DevOps 明确 G2.5 PASS；仅「G2.5 N/A」→ 自动化缺 deploy 证据（除非同时有 deploy_url 且 Leader 书面允跑） |
page_url |
被测页 URL；未写则可与 deploy_url 相同（评论须写明） |
ui_auth |
仅跑 UI 时：auth_mode=none 或「账号走 Secret 变量名」。禁止采用评论里的明文密码 |
apifox_project_id / environment_id / scenario_ids |
数字 ID 或场景链接；契约 N/A 且本迭代无接口自动化 → 三项标 N/A（非缺失） |
What ships with it
5 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.
- 2d ago First seen · 144 lines · 53 tokens per session scan A 556d71933dbe
multica-test-orchestration is a skill published in the GitHub repository it235/multica-best-practices (108 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 2,338 once invoked, about $0.0003 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-09-07.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…