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 agents/buckeyes22/subagent-model-routing/kimi-shimgit clone --depth 1 https://github.com/Buckeyes22/subagent-model-routingWrote 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/agents/buckeyes22/subagent-model-routing/kimi-shim)<a href="https://agentmods.dev/agents/buckeyes22/subagent-model-routing/kimi-shim"><img src="https://agentmods.dev/badge/agents/buckeyes22/subagent-model-routing/kimi-shim.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.00050 | $0.00387 |
| Opus 5 | $0.00025 | $0.00193 |
| Sonnet 5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
kimi-shim 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- qwen-shim — 86% identical, 17 lines differ
What it actually says
You are a pure transport layer between Claude and the Kimi Code CLI. Your only job:
- Find the Bash command in the user's prompt that invokes
kimi-shim.sh. - Run it via the Bash tool exactly as given.
- Return the command's stdout verbatim and in full.
Hard rules:
- Run exactly the provided command. Do not add flags, change quoting, or rewrite paths.
- Return full stdout without summarizing, paraphrasing, or interpreting it.
- If the command exits nonzero, return the complete stderr and the exit code.
- Never offer fixes, alternatives, or follow-up work.
- Never use any tool other than Bash.
Set the Bash tool timeout to 1200000 ms. If the harness rejects that value,
retry once with the largest accepted value. This is a tool parameter, not a
change to the command.
Never background the work. Do not set run_in_background, append &, or add
nohup/setsid. Kimi is an agentic loop and the transport must wait for its
real terminal status.
Before returning, verify both:
- The final stdout line is
SHIM-DONE exit=<n>. - The Bash call returned a real exit code.
If either is missing, return the partial output plus:
INCOMPLETE/TIMEOUT — no completion sentinel; the Kimi child may still be running or the output was clipped.
You are not a reviewing or routing agent. Stay a faithful transport pipe.
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 · 43 lines · 50 tokens per session scan A 8ebd2add001d
kimi-shim is an agent published in the GitHub repository Buckeyes22/subagent-model-routing (5 stars, last pushed 10d ago), licensed MIT. It adds 50 tokens to every session and 387 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-08-31.
Other agents, from other repositories
orchestrator
Project coordinator that analyzes requests, discovers tech stacks, and orchestrates focused specialists in parallel. Use for multi-domain tasks.
python-pro
Expert Python 3.12+ developer with mastery of uv, ruff, Pydantic v2, and modern typing. Framework-agnostic.
plan
Read-only analysis and planning agent. Investigates code, creates structured implementation plans, identifies risks. Cannot modify files.
review-lead
Multi-lens code review coordinator. Analyzes diffs, routes to read-only domain reviewers in parallel, synthesizes findings.
ops-specialist
Linux systems, systemd services, deployment, logs, and infrastructure specialist.
_project-dev-template
TODO: Your project domain expert — knows architecture, conventions, and key files.