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.
git clone --depth 1 https://github.com/luanmorenommaciel/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/luanmorenommaciel/kimi-plugin-cc/kimi-explore)<a href="https://agentmods.dev/commands/luanmorenommaciel/kimi-plugin-cc/kimi-explore"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/kimi-explore/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/luanmorenommaciel/kimi-plugin-cc/kimi-explore"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/kimi-explore.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.00032 | $0.00434 |
| Opus 5.5 | $0.00013 | $0.00174 |
| Sonnet 5.5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
kimi:explore 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 2mo 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
/kimi:explore
Structured codebase analysis: Executive Summary + Health Score + Architecture Deep Dive.
Usage
/kimi:explore how does the auth module work?
/kimi:explore find all database connection code
/kimi:explore --background give me an architecture overview
/kimi:explore # generic analysis when no question is given
Process
-
Load explore prompt template
Read("plugins/kimi/prompts/explore.md") -
Dispatch to Kimi
- The free-text question is the primary input; when no question is given, fall back to a generic codebase analysis.
- Use the
explorerole (--role explore).
Bash("node plugins/kimi/scripts/broker.mjs dispatch \ --prompt '<question>' \ --role explore \ --mode explore \ [--background]")Fallback prompt when no question: "Analyze the codebase at $(pwd). Follow the explore prompt template."
-
Parse and render
- Parse JSON output for
summary,healthScore,techStack,insights,architecture. - Render as a markdown report.
- Parse JSON output for
Output
## 🎯 Executive Summary
...
### Health Score: 8/10
...
### Tech Stack
...
### Key Insights
...
Notes
- Runs under the broker's
--role explore: the read-only role prompt inplugins/kimi/roles/explore.mdis composed into the head of the-pprompt (--agent-fileYAMLs no longer exist in Kimi Code 0.x). - Read-only enforcement is a prompt-level contract — 0.x cannot exclude tools headlessly.
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.
- 2mo ago First seen · 61 lines · 32 tokens per session scan A 800ecfbe2074
kimi:explore is a command published in the GitHub repository luanmorenommaciel/kimi-plugin-cc (14 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 434 once invoked, about $0.0001 per session on Opus 5.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.
kimi:explore compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| kimi:exploreluanmorenommaciel/kimi-plugin-cc | Command | 14 | 3mo ago | MIT | A | 32 | Claude Code |
| checklistgithub/spec-kit | Command | 149k | today | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 149k | today | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 149k | today | MIT | A | 13 | Claude Code |
| convergegithub/spec-kit | Command | 149k | today | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 149k | today | MIT | A | 14 | Claude Code |
| speckit.bug.fixgithub/spec-kit | Command | 149k | today | MIT | A | 12 | Claude Code |