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 commands/satasuk03/kimi-plugin-cc/reasongit 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/commands/satasuk03/kimi-plugin-cc/reason)<a href="https://agentmods.dev/commands/satasuk03/kimi-plugin-cc/reason"><img src="https://agentmods.dev/badge/commands/satasuk03/kimi-plugin-cc/reason.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.00023 | $0.00912 |
| Opus 5 | $0.00012 | $0.00456 |
| Sonnet 5 | $0.00005 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
reason 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
Invoke the kimi:kimi-reasoner subagent via the Agent tool (subagent_type: "kimi:kimi-reasoner"), forwarding the raw user request as the prompt.
kimi:kimi-reasoner is a subagent, not a skill — do not call Skill(kimi:kimi-reasoner) (no such skill) or Skill(kimi:reason) (that re-enters this command and hangs the session). The command runs inline so the Agent tool stays in scope; forked general-purpose subagents do not expose it.
The final user-visible response must be Kimi's output verbatim.
Raw user request: $ARGUMENTS
Core constraint:
- This command is read-only. Kimi should investigate, analyze, and report — not edit files.
Execution mode:
- If the request includes
--background, run thekimi:kimi-reasonersubagent in the background. - If the request includes
--wait, run thekimi:kimi-reasonersubagent in the foreground. - If neither flag is present, default to foreground.
--backgroundand--waitare execution flags for Claude Code. Do not forward them toreason, and do not treat them as part of the natural-language request text.--modelis a runtime-selection flag. Preserve it for the forwardedreasoncall, but do not treat it as part of the natural-language request text.- If the request includes
--resume, do not ask whether to continue. The user already chose. - If the request includes
--fresh, do not ask whether to continue. The user already chose. - Otherwise, before starting Kimi, check for a resumable reasoning thread from this Claude session by running:
node "${CLAUDE_PLUGIN_ROOT}/scripts/kimi-companion.mjs" task-resume-candidate --json
- If that helper reports
available: true, useAskUserQuestionexactly once to ask whether to continue the current Kimi thread or start a new one. - The two choices must be:
Continue current Kimi threadStart a new Kimi thread
- If the user is clearly giving a follow-up instruction such as "continue", "keep going", "resume", or "dig deeper", put
Continue current Kimi thread (Recommended)first. - Otherwise put
Start a new Kimi thread (Recommended)first. - If the user chooses continue, add
--resumebefore routing to the subagent. - If the user chooses a new thread, add
--freshbefore routing to the subagent. - If the helper reports
available: false, do not ask. Route normally.
Operating rules:
- The subagent is a thin forwarder only. It should use one
Bashcall to invokenode "${CLAUDE_PLUGIN_ROOT}/scripts/kimi-companion.mjs" reason ...and return that command's stdout as-is. - Return the Kimi companion stdout verbatim to the user.
- Do not paraphrase, summarize, rewrite, or add commentary before or after it.
- Do not ask the subagent to inspect files, monitor progress, poll
/kimi:status, fetch/kimi:result, call/kimi:cancel, summarize output, or do follow-up work of its own. - Leave the model unset unless the user explicitly asks for one. When unset, the companion runs the reasoning job on Kimi K3 (
kimi-code/k3); when the user names a model, pass the requested id through with--model <id>. - Leave
--resumeand--freshin the forwarded request. The subagent handles that routing when it builds thereasoncommand. - If the helper reports that Kimi is missing or unauthenticated, stop and tell the user to run
/kimi:setup. - If the user did not supply a request, ask what Kimi should analyze, investigate, or reason about.
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 · 52 lines · 23 tokens per session scan A 939d01d5c765
reason is a command published in the GitHub repository satasuk03/kimi-plugin-cc (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 912 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 commands, from other repositories
edison.list
This obsolete slash command is disabled for this repository.
swarm
Fan out a parallel review across the workspace using Kimi's AgentSwarm tool, bounded by a hard wall-clock budget. Read-only by default (enforced by the same PreToolUse hook as review, applied to every subagent); --write fans out edits in a throwaway worktree and returns a patch.
pursue
Hand Kimi an objective to pursue AUTONOMOUSLY across multiple turns (experimental goal mode), bounded by a hard wall-clock budget. Write-capable, gated by the same PreToolUse hook as rescue.
cancel
Cancel an active plugin-managed Kimi job for the current repository.
rescue
Run a write-capable Kimi rescue against the current repository with optional background execution and resume behavior.
review
Run a read-only Kimi review over the current working tree changes or a base ref diff.