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/setupgit clone --depth 1 https://github.com/satasuk03/kimi-plugin-ccWhat 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.00011 | $0.00246 |
| Opus 5 | $0.00005 | $0.00123 |
| Sonnet 5 | $0.00002 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
setup 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 2d 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
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/kimi-companion.mjs" setup --json
If the result says Kimi is unavailable and npm is available:
- Use
AskUserQuestionexactly once to ask whether Claude should install Kimi now. - Put the install option first and suffix it with
(Recommended). - Use these two options:
Install Kimi (Recommended)Skip for now
- If the user chooses install, run:
npm install -g @moonshot-ai/kimi-code
- Then rerun:
node "${CLAUDE_PLUGIN_ROOT}/scripts/kimi-companion.mjs" setup --json
If Kimi is already installed or npm is unavailable:
- Do not ask about installation.
Output rules:
- Present the final setup output to the user.
- If installation was skipped, present the original setup output.
- If Kimi is installed but not authenticated, preserve the guidance to run
!kimi login.
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.
- 2d ago First seen · 37 lines · 11 tokens per session scan A e8b0bd40752c
setup is a command published in the GitHub repository satasuk03/kimi-plugin-cc (2 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 246 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.
papi-audit
Audit the latest changes in this branch for bugs and compliance with the project's conventions defined in CLAUDE.md.
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.
challenge
Run a read-only Kimi challenge review that challenges assumptions and surfaces safer alternatives.