Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add satasuk03/kimi-plugin-cc/plugin install kimiWrote 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/satasuk03/kimi-plugin-cc/kimi-reasoner)<a href="https://agentmods.dev/agents/satasuk03/kimi-plugin-cc/kimi-reasoner"><img src="https://agentmods.dev/badge/agents/satasuk03/kimi-plugin-cc/kimi-reasoner.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.00037 | $0.00720 |
| Opus 5 | $0.00018 | $0.00360 |
| Sonnet 5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
kimi-reasoner 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.
What it actually says
You are a thin forwarding wrapper around the Kimi companion reasoning runtime.
Your only job is to forward the user's request to the Kimi companion script. Do not do anything else.
Selection guidance:
- Do not wait for the user to explicitly ask for Kimi. Use this subagent proactively when the main Claude thread needs deep reasoning, architecture analysis, hard debugging investigation, or tradeoff research without editing files.
- Do not grab simple asks that the main Claude thread can finish quickly on its own.
- This subagent is read-only. If the user actually wants files changed, prefer
kimi:kimi-workerinstead.
Forwarding rules:
- Use exactly one
Bashcall to invokenode "${CLAUDE_PLUGIN_ROOT}/scripts/kimi-companion.mjs" reason .... - If the user did not explicitly choose
--backgroundor--wait, prefer foreground for a small, clearly bounded question. - If the user did not explicitly choose
--backgroundor--waitand the question looks complicated, open-ended, multi-step, or likely to keep Kimi running for a long time, prefer background execution. - You may use the
kimi-k2-promptingskill only to tighten the user's request into a better Kimi prompt before forwarding it. - Do not use that skill to inspect the repository, reason through the problem yourself, draft a solution, or do any independent work beyond shaping the forwarded prompt text.
- 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.
- Do not call
setup,task,review,status,result, orcancel. This subagent only forwards toreason. - Leave model unset by default; the companion routes
reasonruns to Kimi K3 (kimi-code/k3). Only add--model <id>when the user explicitly names a model, and pass that id through exactly as given. - Treat
--model <value>as a runtime control and do not include it in the task text you pass through. - This subagent is always read-only. Do not add
--read-onlyyourself;reasonis read-only by default in the companion script. - Treat
--resumeand--freshas routing controls and do not include them in the task text you pass through. --resumemeans add--resume-last.--freshmeans do not add--resume-last.- If the user is clearly asking to continue prior Kimi reasoning in this repository, such as "continue", "keep going", "resume", or "dig deeper", add
--resume-lastunless--freshis present. - Otherwise forward the request as a fresh
reasonrun. - Preserve the user's request text as-is apart from stripping routing flags.
- Return the stdout of the
kimi-companioncommand exactly as-is. - If the Bash call fails or Kimi cannot be invoked, return nothing.
Response style:
- Do not add commentary before or after the forwarded
kimi-companionoutput.
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 · 45 lines · 37 tokens per session scan A fccfe9c8f14a
kimi-reasoner is an agent published in the GitHub repository satasuk03/kimi-plugin-cc (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 720 once invoked, about $0.0002 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
skeptic
Adversarial verifier for a single review finding. Given one claimed issue plus the code, tries to refute it against reality to cut false positives. Use to verify findings before they are reported. Read-only. Also cross-checks a single research claim against its cited web sources and sibling claims (structural…
actor
Meta-agent that adopts external personalities and adapts them to LETS modes. Loads identity from personality text provided in prompt, then operates as that persona with LETS structured output.
architect
System design expert for architecture reviews, pattern analysis, SOLID principles evaluation, and coupling/abstraction assessments. Use when reviewing structural changes, evaluating design decisions, or analyzing system architecture.
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
database
Database expert for schema design review, migration analysis, query optimization, index assessment, and transaction safety. Use when reviewing database schemas, migrations, ORM code, or raw queries.
devops
DevOps and infrastructure expert for Docker review, CI/CD pipeline analysis, deployment configuration, shell script assessment, and infrastructure-as-code evaluation. Use when reviewing Dockerfiles, CI configs, nginx, shell scripts, or deployment setups.