index

A command that builds or refreshes a map of the named parts of your code, such as functions, classes, and methods.

In plain words
What is it for?
Use it to create the first code map, force a clean rebuild, or inspect indexing results such as symbols found, files covered, and the tools used for each language.
Why use it?
It gives code-search commands an up-to-date structure to work from, so you do not have to rebuild the map by hand. Most searches update it automatically.

Command

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.

agentmods
npx agentmods add commands/benmarte/codemunch/index
Clone the repo
git clone --depth 1 https://github.com/benmarte/codemunch
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 164 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00011 $0.00164
Opus 5 $0.00005 $0.00082
Sonnet 5 $0.00002 $0.00033
Haiku 4.5 $0.00001 $0.00016

Measured yesterday against content hash 86dc81c9cd2c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

index 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 yesterday.

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.

commands/index.md · 16 lines

What it actually says

Run the detect-lsp skill to configure engines, then run the index skill to build the symbol map.

Note: You usually don't need to run this manually. The index auto-updates whenever you use /codemunch:search, /codemunch:fetch, /codemunch:refs, or /codemunch:explore. Use /codemunch:index --force if you want a clean rebuild.

After indexing report:

  • Total symbols found
  • Files indexed
  • Engine used per language (LSP / ctags / rg)
  • Top 5 files by symbol count
  • "Run /codemunch:search to look up any symbol"
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. yesterday First seen · 16 lines · 11 tokens per session scan A 86dc81c9cd2c

Subscribe to this mod's changes

index is a command published in the GitHub repository benmarte/codemunch (7 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 164 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.