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 YeSongYun/openclaw-cn --skill acp-routergit clone --depth 1 https://github.com/YeSongYun/openclaw-cnWrote 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/yesongyun/openclaw-cn/acp-router)<a href="https://agentmods.dev/skills/yesongyun/openclaw-cn/acp-router"><img src="https://agentmods.dev/badge/skills/yesongyun/openclaw-cn/acp-router/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/yesongyun/openclaw-cn/acp-router"><img src="https://agentmods.dev/badge/skills/yesongyun/openclaw-cn/acp-router.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.00069 | $0.01951 |
| Opus 5 | $0.00034 | $0.00975 |
| Sonnet 5 | $0.00014 | $0.00390 |
| Haiku 4.5 | $0.00007 | $0.00195 |
Grade A, and why
acp-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 12d 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.
This is a copy
100% identical to acp-router — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACP Harness Router
When user intent is "run this in Pi/Claude Code/Codex/OpenCode/Gemini/Kimi (ACP harness)", do not use subagent runtime or PTY scraping. Route through ACP-aware flows.
Intent detection
Trigger this skill when the user asks OpenClaw to:
- run something in Pi / Claude Code / Codex / OpenCode / Gemini
- continue existing harness work
- relay instructions to an external coding harness
- keep an external harness conversation in a thread-like conversation
Mandatory preflight for coding-agent thread requests:
- Before creating any thread for Pi/Claude/Codex/OpenCode/Gemini work, read this skill first in the same turn.
- After reading, follow
OpenClaw ACP runtime pathbelow; do not usemessage(action="thread-create")for ACP harness thread spawn.
Mode selection
Choose one of these paths:
- OpenClaw ACP runtime path (default): use
sessions_spawn/ ACP runtime tools. - Direct
acpxpath (telephone game): useacpxCLI throughexecto drive the harness session directly.
Use direct acpx when one of these is true:
- user explicitly asks for direct
acpxdriving - ACP runtime/plugin path is unavailable or unhealthy
- the task is "just relay prompts to harness" and no OpenClaw ACP lifecycle features are needed
Do not use:
subagentsruntime for harness control/acpcommand delegation as a requirement for the user- PTY scraping of pi/claude/codex/opencode/gemini/kimi CLIs when
acpxis available
AgentId mapping
Use these defaults when user names a harness directly:
- "pi" ->
agentId: "pi" - "claude" or "claude code" ->
agentId: "claude" - "codex" ->
agentId: "codex" - "opencode" ->
agentId: "opencode" - "gemini" or "gemini cli" ->
agentId: "gemini" - "kimi" or "kimi cli" ->
agentId: "kimi"
These defaults match current acpx built-in aliases.
If policy rejects the chosen id, report the policy error clearly and ask for the allowed ACP agent id.
OpenClaw ACP runtime path
Required behavior:
- For ACP harness thread spawn requests, read this skill first in the same turn before calling tools.
- Use
sessions_spawnwith:runtime: "acp"thread: truemode: "session"(unless user explicitly wants one-shot)
- For ACP harness thread creation, do not use
messagewithaction=thread-create;sessions_spawnis the only thread-create path. - Put requested work in
taskso the ACP session gets it immediately. - Set
agentIdexplicitly unless ACP default agent is known. - Do not ask user to run slash commands or CLI when this path works directly.
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.
- 12d ago First seen · 220 lines · 69 tokens per session scan A 80f5a6382fa6
acp-router is a skill published in the GitHub repository YeSongYun/openclaw-cn (56 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 1,951 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to acp-router, differing in 0 lines, and is treated as a copy.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…