enable

A command that turns codemunch's project enforcement back on.

In plain words
What is it for?
Use it after enforcement was disabled to enable the pre-tool check and restore codemunch rules in CLAUDE.md.
Why use it?
It restores the checks and project instructions that help require codemunch for code exploration.

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/enable
Clone the repo
git clone --depth 1 https://github.com/benmarte/codemunch
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 197 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.00021 $0.00197
Opus 5 $0.00010 $0.00098
Sonnet 5 $0.00004 $0.00039
Haiku 4.5 $0.00002 $0.00020

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

Security

Grade A, and why

enable 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/enable.md · 26 lines

What it actually says

Re-enable codemunch enforcement for this project. Do both steps:

Step 1: Enable the PreToolUse hook

Write or update .claude/codemunch/config.json to set hook_enabled to true. If the file exists, preserve other settings and only change hook_enabled. If it doesn't exist, create it:

{
  "hook_enabled": true
}

Step 2: Restore CLAUDE.md enforcement rules

Run /codemunch:init to add the enforcement rules back to CLAUDE.md. If the codemunch section already exists, skip this step.

After both steps

Report:

  • "codemunch enforcement enabled. The hook and CLAUDE.md rules are active."
  • "Run /codemunch:disable to turn off enforcement."
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 · 26 lines · 21 tokens per session scan A 523bc9ca210c

Subscribe to this mod's changes

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