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/techysy/10routerWrote 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/techysy/10router/sync-usage)<a href="https://agentmods.dev/commands/techysy/10router/sync-usage"><img src="https://agentmods.dev/badge/commands/techysy/10router/sync-usage/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/techysy/10router/sync-usage"><img src="https://agentmods.dev/badge/commands/techysy/10router/sync-usage.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.00140 | $0.00604 |
| Opus 5.5 | $0.00056 | $0.00242 |
| Sonnet 5.5 | $0.00028 | $0.00121 |
| Haiku 4.5 | $0.00014 | $0.00060 |
Grade A, and why
sync-usage 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
Export ZCode model-usage records into 10Router by running the plugin's export script.
Steps:
- Determine the mode: if this machine can reach the 10Router endpoint, sync online. If it cannot (different network / no route), export offline:
--export zcode-usage.json(no endpoint or credentials needed), tell the user to carry the file to a machine that can reach 10Router, and give them the import command (--import zcode-usage.json --endpoint <URL> --key <sk-…>). - Determine the 10Router endpoint: default
http://127.0.0.1:20127; if the user gave an address in $ARGUMENTS (e.g. a NAS IP), use it via--endpoint. - Determine credentials: use
--key sk-…(virtual key from 10Router dashboard → API Keys, recommended) or--password. If neither is known, ask the user for one. - Run a dry-run first and summarize what would be exported:
node "$ZCODE_PLUGIN_ROOT/scripts/export-usage.mjs" --endpoint <URL> --key <sk-…> --dry-run
- If the dry-run looks right (non-zero rows, sensible provider split), run the real import and report the
imported X, skipped Yresult. The operation is idempotent — safe to re-run. - If the user writes in Chinese, respond in Chinese.
- To sync a non-ZCode source, pass
--source opencode/--source mirasim/--source mimo/--source 10r(they are not auto-detected; "全平台" means running all sources one by one).--source 10rreads another 10Router/9Router instance'sdata.sqlite(auto-discovered locally, or--db <path>for a NAS copy / mounted share; the script refuses to import a db that belongs to the very instance behind a loopback--endpoint— use--forceonly if it truly is a different instance).
Arguments (all optional): $ARGUMENTS
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 · +1 lines · +46 tokens per session 26f482afaff2
- 1mo ago Changed · +42 tokens per session 577c4f683297
- 1mo ago Changed · +20 tokens per session 6b8e2cd9c95c
- 1mo ago Changed · +1 lines · +7 tokens per session 466649a9f04d
- 1mo ago First seen · 21 lines · 25 tokens per session scan A d7ac1cd03c0e
sync-usage is a command published in the GitHub repository techysy/10router (93 stars, last pushed today), licensed MIT. It adds 140 tokens to every session and 604 once invoked, about $0.0006 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-09-06.
Other commands, from other repositories
triage
Triage Linear issue with comprehensive analysis.
router-feedback
Submit feedback about router decision or model performance.
card
Open one self-contained OverClick card.
check
View the latest screenshot from /Pictures/Screenshots.
bmad-editorial-review-structure
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure.
bmad-prfaq
Working Backwards PRFAQ challenge that stress-tests a product concept customer-first. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.