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/kylinmountain/nano-claw/coding-routernpx skills add KylinMountain/nano-claw --skill coding-routergit clone --depth 1 https://github.com/KylinMountain/nano-clawWrote 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/kylinmountain/nano-claw/coding-router)<a href="https://agentmods.dev/skills/kylinmountain/nano-claw/coding-router"><img src="https://agentmods.dev/badge/skills/kylinmountain/nano-claw/coding-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 | $0.00016 | $0.00328 |
| Opus 5 | $0.00008 | $0.00164 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
coding-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 5d 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
Coding Router Skill
Purpose
This skill helps decide whether to:
- Solve coding tasks directly with local tools, or
- Delegate to the external coding CLI via
run_external_coder.
Decision Rules
Prefer local tools when:
- The change is small and file-scoped.
- You already have enough context.
- Fast iteration with direct edits is best.
Prefer external coder when:
- The request is broad, multi-file, or architecture-level.
- The user explicitly asks to use Gemini CLI / Codex.
- You need specialized coding-agent behavior.
Workflow
- Briefly explain your plan.
- Gather minimal context (read/search files).
- Decide local vs delegated execution.
- If delegated, call
run_external_coderwith a precisetaskand optionalcontext. - Validate results (tests/lint/build if relevant).
- Summarize what changed, risks, and next steps.
Safety
- Respect current approval policy and confirmation flow.
- Never expose secrets in task/context payloads.
- Keep delegated tasks scoped to the current workspace.
Delegation Prompt Quality
When calling run_external_coder, include:
- Goal and constraints
- Relevant files/paths
- Acceptance criteria
- Required validation commands
Example task structure:
- Objective: Fix failing tests in module X
- Constraints: Keep public API unchanged
- Validation:
pytest tests/test_x.py -q
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.
- 5d ago First seen · 54 lines · 16 tokens per session scan A f000ef31b378
coding-router is a skill published in the GitHub repository KylinMountain/nano-claw (4 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 328 once invoked, about $0.0001 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
architecture
Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
issue-brief
Explain a GitHub issue, discussion, or feature request in plain language before deciding whether to build it. Covers what the reporter actually wants, a numbered walkthrough of the failure using real hostnames/ports/endpoints, how the code behaves today with file:line anchors, what implementing it would take, and the…
bug-audit
Weekly multi-agent audit for serious bugs (data integrity, silent caps, staleness, timestamp math, trust boundaries). Fans out Sonnet scanners + Opus deep auditors, adversarially verifies every finding, files GitHub issues for confirmed critical/high bugs. Trigger: /bug-audit.
async-job-orchestration
Manage long-running async LLM jobs across Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. Use for parallel or non-blocking execution. Covers backend-qualified durability, cache-aware promptParts, cache-state:// MCP resources, and the Claude cachettlexpiringsoon warning.
multi-llm-review
Run complete, evidence-backed code reviews through the local stdio gateway across the seven canonical CLI providers: Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. Use for quality, security, correctness, or release validation that requires independent reviewers.