What is codemunch CLAUDE.md?

A set of release instructions for the Codemunch project. It requires updating the changelog, version, documentation, and project checks before publishing a GitHub release.

Use it when preparing a Codemunch release, reviewing commits since the previous version, checking plugin structure, and creating the GitHub release.

It reduces the chance of releasing undocumented changes, incorrect version numbers, or an invalid plugin.

codemunch CLAUDE.md — Instructions file by benmarte

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 instructions/benmarte/codemunch/claude-md

Clone the repo

git clone --depth 1 https://github.com/benmarte/codemunch

Per session 469 This file is loaded in full into every session.

When invoked 469 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5	$0.00469	$0.00469
Opus 5	$0.00234	$0.00234
Sonnet 5	$0.00094	$0.00094
Haiku 4.5	$0.00047	$0.00047

Measured 2d ago against content hash fea34bf833cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

codemunch CLAUDE.md 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

autoimprove CLAUDE.md — 89% identical, 8 lines differ

CLAUDE.md · 47 lines

What it actually says

Project Rules

Release Checklist

Before cutting a new release, ALL of the following must be completed. Do not create the GitHub release until every item is done.

1. Changelog

Create or update CHANGELOG.md with a new entry for the version
Use Keep a Changelog format: Added, Changed, Fixed, Removed
Every commit since the last release must be accounted for

2. Version Bump

Update VERSION file to the new version number
Follow semver: breaking changes = major, new features = minor, bug fixes = patch

3. README

Update README.md to reflect any new features, changed behavior, or removed functionality
Update any version numbers referenced in examples
Add new commands/options to the Commands table if applicable
Update the "Plugin structure" tree if files were added/removed

4. Pre-release Verification

git status must be clean (all changes committed)
Review git log --oneline v{LAST}..HEAD to confirm nothing was missed
Verify the plugin structure is valid (all skills have SKILL.md, hooks are executable)

5. Create Release

Commit all of the above first
Push to main
Create GitHub release with gh release create v{VERSION}
Release notes should summarize changes (not duplicate the full changelog)
Include a link to the full changelog in the release notes

Semantic Versioning

Major (X.0.0) — Breaking changes that require users to change how they use the plugin
Minor (1.X.0) — New features or enhancements that are backwards-compatible
Patch (1.1.X) — Bug fixes only, no new functionality

Files to Never Modify During Automated Runs

LICENSE
.claude-plugin/marketplace.json

Commit Style

Use imperative mood: "Add feature" not "Added feature"
Keep subject line under 72 characters
Include Co-Authored-By: Claude Opus 4.6 <[email protected]> when Claude writes the commit

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.

2d ago First seen · 47 lines · 469 tokens per session scan A fea34bf833cb

Subscribe to this mod's changes

codemunch CLAUDE.md is an instructions file published in the GitHub repository benmarte/codemunch (7 stars, last pushed 5mo ago), licensed MIT. It adds 469 tokens to every session, about $0.0023 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.

Git and workflow Releases ai ai-skill claude claude-ai claude-code claude-code-plugin

autoimprove CLAUDE.md

Instructions for benmarte/autoimprove, covering project rules, release checklist, 1. changelog, 2. version bump and 3. readme.

benmarte/autoimprove · 414 tokens

mcp-server-excel coverage-prevention-strategy.instructions.md

Instructions for sbroenne/mcp-server-excel, covering generated surface coverage, contract change workflow, required checks and common incomplete changes.

sbroenne/mcp-server-excel · 396 tokens

azure-sdk-for-rust changelog.instructions.md

Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.

Azure/azure-sdk-for-rust · 164 tokens

codemunch CLAUDE.md