agentmods.dev

kimi:explore

kimi:explore is a command for Claude Code from luanmorenommaciel/kimi-plugin-cc. It costs 32 tokens per session (434 once invoked), scanned A, original, MIT.

A command for exploring a codebase and producing a report about its purpose, health, technologies, and architecture. It can answer a specific question or give a general overview.

In plain words
What is it for?
Use it to investigate modules, trace implementation details, find related code, or get an architecture summary without changing files.
Why use it?
It reduces the time needed to understand unfamiliar code and locate where a particular feature, such as database connections, is implemented.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the kimi plugin — 2 skills, 12 commands, 1 agent shipped together

not rated 12repo +2 1mo ago A scan 32 tokens original MIT

Good fit Use it to investigate modules, trace implementation details, find related code, or get an architecture summary without changing files.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/luanmorenommaciel/kimi-plugin-cc/kimi-explore
View source ↗ luanmorenommaciel/kimi-plugin-cc
Install

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.

Clone the repo
git clone --depth 1 https://github.com/luanmorenommaciel/kimi-plugin-cc

Made for: Claude Code.

Or install kimi, the plugin that ships this one along with the rest of its 2 skills, 12 commands, 1 agent.

Wrote 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.

agentmods badge for kimi:explore

README.md
[![agentmods](https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/kimi-explore.svg)](https://agentmods.dev/commands/luanmorenommaciel/kimi-plugin-cc/kimi-explore)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 434 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00434
Opus 5 $0.00016 $0.00217
Sonnet 5 $0.00006 $0.00087
Haiku 4.5 $0.00003 $0.00043

Measured 8d ago against content hash 800ecfbe2074, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 8d 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.

plugins/kimi/commands/kimi:explore.md · 61 lines

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

  1. Load explore prompt template

    Read("plugins/kimi/prompts/explore.md")

  2. 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 explore role (--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."

  3. Parse and render

    • Parse JSON output for summary, healthScore, techStack, insights, architecture.
    • Render as a markdown report.

Output

## 🎯 Executive Summary
...
### Health Score: 8/10
...
### Tech Stack
...
### Key Insights
...

Notes

  • Runs under the broker's --role explore: the read-only role prompt in plugins/kimi/roles/explore.md is composed into the head of the -p prompt (--agent-file YAMLs no longer exist in Kimi Code 0.x).
  • Read-only enforcement is a prompt-level contract — 0.x cannot exclude tools headlessly.
Changes

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.

  1. 8d ago First seen · 61 lines · 32 tokens per session scan A 800ecfbe2074

Subscribe to this mod's changes

kimi:explore is a command published in the GitHub repository luanmorenommaciel/kimi-plugin-cc (12 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 434 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.

Research
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens