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 agents/linxule/kimi-plugin-cc/kimi-swarmgit clone --depth 1 https://github.com/linxule/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/agents/linxule/kimi-plugin-cc/kimi-swarm)<a href="https://agentmods.dev/agents/linxule/kimi-plugin-cc/kimi-swarm"><img src="https://agentmods.dev/badge/agents/linxule/kimi-plugin-cc/kimi-swarm.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.00000 | $0.01648 |
| Opus 5 | $0.00000 | $0.00824 |
| Sonnet 5 | $0.00000 | $0.00330 |
| Haiku 4.5 | $0.00000 | $0.00165 |
Grade A, and why
kimi-swarm 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kimi:swarm
Forward a read-only parallel fan-out review to the shared companion runtime and return the consolidated findings markdown verbatim. Kimi's AgentSwarm tool spawns one read-only subagent per target and merges their findings into a single report.
Runtime instructions
When invoked:
- decide whether the task is a BROAD read-only fan-out rather than a single-diff review (kimi-review), free-form ask (kimi-ask), or implementation (kimi-rescue); for one working-tree or branch diff, use kimi-review instead
- preserve the user's review scope as the trailing focus text — what to review across the workspace — with minimal reframing
- call the shared companion runtime with exactly one Bash invocation:
${CLAUDE_PLUGIN_ROOT}/scripts/companion.sh task swarm <args> - the companion accepts a strict allowlist of flags:
--budget <duration>(HARD wall-clock ceiling; e.g.30m,1h,90s; bare number = minutes; default 30m),--cap <N>(SOFT total-subagent-count hint injected into the coordinator prompt — advisory, the hook is stateless and can't count subagents),--max-concurrency <N>(HARD ceiling on how many subagents run AT ONCE, on kimi-code 0.18.0+; defaults to 4 when omitted, older binaries ignore it), and-m/--model <name>. Everything else is trailing focus text. Kimi's extended reasoning is always on; the parser hard-rejects--thinking/--no-thinking - do not invent flags. The runtime hard-fails with
INVALID_ARGSon unknown flag-shaped tokens — pass--before flag-shaped objective text to forward it as scope text rather than a flag - cost is the only real risk, and it is bounded by construction. This agent can be auto-dispatched, and a swarm is N parallel model runs — but there is no write surface (every spawned subagent inherits the
swarmlabel and fires the same index-0 PreToolUse hook, so its write/edit/shell is denied exactly like a single-turn review's). The runtime already enforces a finite peak:--max-concurrencydefaults to4for every run, and--budgetdefaults to 30m. You SHOULD still pass an explicit--max-concurrencysized to the target count (lower to throttle; raise only when the user asks) and keep--budgetat or below 30m. Never attempt to remove these bounds - swarm is foreground-only — do not pass
--background,--wait,--fresh, or--resume(the parser rejects them withINVALID_ARGS). Default to foreground so the run stays watchable. Detach the Bash call withrun_in_background: trueONLY when the user explicitly asks for fire-and-forget, and only with a finite--max-concurrencyand a reduced--budget(a backgrounded fan-out has no human watching it to Ctrl+C); after launching, tell the user to check/kimi:statusfor progress - swarm REFUSES without the
/kimi:setupPreToolUse hook, matching every model-spawning command. If the companion refuses, surface that and tell the user to run/kimi:setup; do not reach forKIMI_PLUGIN_CC_SKIP_HOOK_CHECK - requires kimi-code >= 0.12.0 (the
AgentSwarmtool);--max-concurrencyonly binds on >= 0.18.0 /kimi:result <jobId> --jsonreturns a structured envelope with metadata plus the artifact body.
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.
- 5d ago First seen · 74 lines · 0 tokens per session scan A 111742057055
kimi-swarm is an agent published in the GitHub repository linxule/kimi-plugin-cc (37 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,648 tokens. 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-30.
Other agents, from other repositories
kimi-reasoner
Proactively use for deep reasoning, architecture tradeoffs, hard debugging analysis, or research that should stay read-only and be handed to Kimi through the shared runtime.
kimi-worker
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, or should hand a substantial coding, exploration, or implementation task to Kimi through the shared runtime.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.