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/satasuk03/kimi-plugin-cc/kimi-cli-runtimenpx skills add satasuk03/kimi-plugin-cc --skill kimi-cli-runtimegit clone --depth 1 https://github.com/satasuk03/kimi-plugin-ccWrote 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/satasuk03/kimi-plugin-cc/kimi-cli-runtime)<a href="https://agentmods.dev/skills/satasuk03/kimi-plugin-cc/kimi-cli-runtime"><img src="https://agentmods.dev/badge/skills/satasuk03/kimi-plugin-cc/kimi-cli-runtime.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.00017 | $0.00779 |
| Opus 5 | $0.00009 | $0.00390 |
| Sonnet 5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
kimi-cli-runtime 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 3d 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
Kimi Runtime
Use this skill only inside the kimi:kimi-worker and kimi:kimi-reasoner subagents.
Primary helpers:
node "${CLAUDE_PLUGIN_ROOT}/scripts/kimi-companion.mjs" task "<raw arguments>"— forkimi:kimi-worker.node "${CLAUDE_PLUGIN_ROOT}/scripts/kimi-companion.mjs" reason "<raw arguments>"— forkimi:kimi-reasoner.
Execution rules:
- Each subagent is a forwarder, not an orchestrator. Its only job is to invoke its one subcommand once and return that stdout unchanged.
- Prefer the helper over hand-rolled
git, directkimiCLI strings, or any other Bash activity. - Do not call
setup,review,status,result, orcancelfrom either subagent. kimi:kimi-workerusestaskfor every request, including diagnosis, planning, research, and explicit implementation requests.kimi:kimi-reasonerusesreasonfor every request.reasonis always read-only, regardless of flags.- You may use the
kimi-k2-promptingskill to rewrite the user's request into a tighter Kimi prompt before the single call. - That prompt drafting is the only Claude-side work allowed. Do not inspect the repo, solve the task yourself, or add independent analysis outside the forwarded prompt text.
- Leave model unset by default. Add
--modelonly when the user explicitly asks for one. - When the user explicitly names a model, pass that id through with
--model <id>exactly as given; otherwise leave it unset. Unset meanstaskruns on Kimi's configureddefault_model, whilereasonruns on Kimi K3 (kimi-code/k3). kimi:kimi-workerdefaults to a write-capable Kimi run. Add--read-onlyonly when the user explicitly asks for read-only behavior or only wants investigation, diagnosis, or research without edits.
Command selection:
- Use exactly one call per handoff.
- If the forwarded request includes
--backgroundor--wait, treat that as Claude-side execution control only. Strip it before calling the subcommand, and do not treat it as part of the natural-language prompt text. - If the forwarded request includes
--model, pass it through as-is. - If the forwarded request includes
--resume, strip that token from the prompt text and add--resume-last. - If the forwarded request includes
--fresh, strip that token from the prompt text and do not add--resume-last. --resume: always add--resume-last, even if the request text is ambiguous.--fresh: always use a fresh run, even if the request sounds like a follow-up.--resume-last: internal helper for "keep going", "resume", "apply the top fix", or "dig deeper" after a previous run.
Safety rules:
- Default to write-capable Kimi work in
kimi:kimi-workerunless the user explicitly asks for read-only behavior. kimi:kimi-reasoneris always read-only.- Preserve the user's request text as-is apart from stripping routing flags.
- Do not inspect the repository, read files, grep, monitor progress, poll status, fetch results, cancel jobs, summarize output, or do any follow-up work of your own.
- Return the stdout of the invoked subcommand exactly as-is.
- If the Bash call fails or Kimi cannot be invoked, return nothing.
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.
- 3d ago First seen · 44 lines · 17 tokens per session scan A 1365c5f8af0a
kimi-cli-runtime is a skill published in the GitHub repository satasuk03/kimi-plugin-cc (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 779 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
kimi-swarm-write
Run a write-capable Kimi swarm that edits many disjoint targets in a throwaway worktree and returns a reviewable patch. Use only for explicit parallel edit fan-out requests; the plugin never applies or commits the patch.
kimi-ask
Ask Kimi a read-only free-form question about the current repository. Use for prose explanations, flow tracing, module comparisons, or conceptual reasoning where Codex should delegate the answer to local kimi-code rather than perform implementation.
kimi-pursue
Run Kimi's autonomous goal mode for an explicitly requested hands-off multi-turn objective. This is write-capable and budget-bounded; use only when the user explicitly asks Kimi to pursue an objective autonomously.
kimi-setup
Verify local Kimi companion readiness and manage the kimi-code PreToolUse hook plus optional review gate state. Use when explicitly requested to install, check, enable, disable, or uninstall the integration. Codex and Claude Code share one /.kimi-code/config.toml but each own a host-scoped block, so $kimi-setup here…
kimi-cancel
Cancel an active plugin-managed Kimi job for the current repository. Use only when the user explicitly asks to cancel a Kimi run.
kimi-challenge
Run a read-only adversarial Kimi challenge review that questions assumptions, design choices, and tradeoffs. Use when the user wants pushback on whether the approach is right, not a defect-only review.