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/commands/satasuk03/kimi-plugin-cc/task)<a href="https://agentmods.dev/commands/satasuk03/kimi-plugin-cc/task"><img src="https://agentmods.dev/badge/commands/satasuk03/kimi-plugin-cc/task/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/satasuk03/kimi-plugin-cc/task"><img src="https://agentmods.dev/badge/commands/satasuk03/kimi-plugin-cc/task.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00883 |
| Opus 5.5 | $0.00007 | $0.00353 |
| Sonnet 5.5 | $0.00004 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
task 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 1mo 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.
This is a copy
88% identical to rescue — 44 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Invoke the kimi:kimi-worker subagent via the Agent tool (subagent_type: "kimi:kimi-worker"), forwarding the raw user request as the prompt.
kimi:kimi-worker is a subagent, not a skill — do not call Skill(kimi:kimi-worker) (no such skill) or Skill(kimi:task) (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
Execution mode:
- If the request includes
--background, run thekimi:kimi-workersubagent in the background. - If the request includes
--wait, run thekimi:kimi-workersubagent in the foreground. - If neither flag is present, default to foreground.
--backgroundand--waitare execution flags for Claude Code. Do not forward them totask, and do not treat them as part of the natural-language task text.--modeland--read-onlyare runtime-selection flags. Preserve them for the forwardedtaskcall, but do not treat them as part of the natural-language task 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 task 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", "apply the top fix", 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" task ...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
--read-onlyunset unless the user explicitly asks for read-only, investigation-only, or no-edits behavior. - Leave the model unset unless the user explicitly asks for one; when they do, pass the requested id through with
--model <id>. - Leave
--resumeand--freshin the forwarded request. The subagent handles that routing when it builds thetaskcommand. - 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 investigate, build, or fix.
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.
- 1mo ago First seen · 50 lines · 18 tokens per session scan A a23e65094418
task is a command published in the GitHub repository satasuk03/kimi-plugin-cc (2 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 883 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to rescue, differing in 44 lines, and is treated as a copy.
Other commands, from other repositories
verify
Fidelity check — rebuild a page from the extracted tokens, pixel-diff it against the live site, and score how faithfully the tokens capture the design.
battle
Head-to-head graded battle card between two sites — eight dimensions, bar-by-bar, verdict line.
zh
A short command that switches Claude Code to Simplified Chinese. It is handled locally by a command hook.
cli-anything-web:list
List all available CLI-Anything-Web CLIs (installed and generated).
stop
Gracefully close the Vibe Squad tmux session from inside Chrono.
note
Add a note to the active task - progress, decisions, context. --session (aliases --snapshot, --pre-compact, --compact) writes a resume-grade session snapshot without ending the session. --team writes a fact or a decision into the standing team's file.