status

A command that reports how codemunch is configured, how current its code map is, and how much it has been used during the session.

In plain words
What is it for?
Use it to check language engines, index age and coverage, changed files that need updating, and session fetch and token-use statistics.
Why use it?
It shows whether searches are working from current code and whether the tool is reducing the amount of code that must be read.

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/status
Clone the repo
git clone --depth 1 https://github.com/benmarte/codemunch
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 302 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.00013 $0.00302
Opus 5 $0.00006 $0.00151
Sonnet 5 $0.00003 $0.00060
Haiku 4.5 $0.00001 $0.00030

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

Security

Grade A, and why

status 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/status.md · 32 lines

What it actually says

Read .claude/codemunch/config.json and .claude/codemunch/index.json and .claude/codemunch/session.log and report:

  1. Engine config — per language: LSP / ctags / rg and which server
  2. Index status — last built, total symbols, files covered, auto-update enabled
  3. Session stats — fetches this session, total tokens used, total tokens saved vs reading full files
  4. Stale check — compare index generated timestamp against git diff --name-only to find files changed since index was built. Report how many files are stale (if any). Note: the index auto-updates on next query, so manual action is rarely needed.

Format:

codemunch status

Engines:
  TypeScript  → typescript-language-server (LSP) ✅
  Python      → ctags ✅  
  Bash        → ripgrep ✅

Index:
  Built:      2026-03-11 02:14 (3 hours ago)
  Symbols:    1,247 across 89 files
  Status:     ✅ fresh (no changes since last index)

Session:
  Fetches:    23
  Tokens used:     ~840
  Tokens saved:    ~186,000
  Savings:         99.5%
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 · 32 lines · 13 tokens per session scan A 31bc24b88a3a

Subscribe to this mod's changes

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