What is jmunch-claude-code-setup CLAUDE.md?

A project instruction file for jmunch-claude-code-setup, a setup that uses code and document navigation services to help an agent work with a codebase. It defines workflow, planning, commit, changelog, and secret-handling rules.

Use it when starting work, planning milestones, updating project files, writing changelog entries, or preparing commits in this repository.

It keeps project work inside the required planning process and prevents unsafe or undocumented changes. It also records the expected commit format and release boundaries.

How shacharbard/jmunch-claude-code-setup configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to shacharbard/jmunch-claude-code-setup. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/shacharbard/jmunch-claude-code-setup/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/shacharbard/jmunch-claude-code-setup

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/shacharbard/jmunch-claude-code-setup/claude-md/github.svg)](https://agentmods.dev/instructions/shacharbard/jmunch-claude-code-setup/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/shacharbard/jmunch-claude-code-setup/claude-md"><img src="https://agentmods.dev/badge/instructions/shacharbard/jmunch-claude-code-setup/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/shacharbard/jmunch-claude-code-setup/claude-md"><img src="https://agentmods.dev/badge/instructions/shacharbard/jmunch-claude-code-setup/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

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.

Model	Per session	Once invoked
Fable 5.1	$0.00718	$0.00718
Opus 5.5	$0.00287	$0.00287
Sonnet 5.5	$0.00144	$0.00144
Haiku 4.5	$0.00072	$0.00072

Measured 2mo ago against content hash a6ec0eefe4c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jmunch-claude-code-setup 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 2mo 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.

CLAUDE.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

jmunch-claude-code-setup

Core value: Enforcement and tracking layer that ensures Claude Code uses jCodeMunch/jDocMunch MCP servers for code/doc navigation, saving 85-95% of tokens

Active Context

Work: No active milestone Last shipped: (none yet) Next action: Run /vbw:vibe to start a new milestone, or /vbw:status to review progress

VBW Rules

Always use VBW commands for project work. Do not manually edit files in .vbw-planning/.
Commit format: {type}({scope}): {description} — types: feat, fix, test, refactor, perf, docs, style, chore.
One commit per task. Each task in a plan gets exactly one atomic commit.
CHANGELOG rule: Every entry in CHANGELOG.md must have a short human-readable explanation — what it does, what it fixes, or what it adds. Never list raw commit messages alone.
Never commit secrets. Do not stage .env, .pem, .key, credentials, or token files.
Plan before building. Use /vbw:vibe for all lifecycle actions. Plans are the source of truth.
Do not fabricate content. Only use what the user explicitly states in project-defining flows.
Do not bump version or push until asked. Never run scripts/bump-version.sh or git push unless the user explicitly requests it, except when .vbw-planning/config.json intentionally sets auto_push to always or after_phase.

Code Intelligence

Prefer LSP over Search/Grep/Glob/Read for semantic code navigation — it's faster, precise, and avoids reading entire files:

goToDefinition / goToImplementation to jump to source
findReferences to see all usages across the codebase
workspaceSymbol to find where something is defined
documentSymbol to list all symbols in a file
hover for type info without reading the file
incomingCalls / outgoingCalls for call hierarchy

Before renaming or changing a function signature, use findReferences to find all call sites first.

Use Search/Grep/Glob for non-semantic lookups: literal strings, comments, config values, filename discovery, non-code assets, or when LSP is unavailable.

Read the full file on GitHub · 49 lines

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.

2mo ago First seen · 49 lines · 718 tokens per session scan A a6ec0eefe4c2

Subscribe to this mod's changes

jmunch-claude-code-setup CLAUDE.md is an instructions file published in the GitHub repository shacharbard/jmunch-claude-code-setup (5 stars, last pushed 7mo ago), licensed MIT. It adds 718 tokens to every session, about $0.0029 per session on Opus 5.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.

jmunch-claude-code-setup CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
jmunch-claude-code-setup CLAUDE.mdshacharbard/jmunch-claude-code-setup	Instructions file	5	7mo ago	MIT	A	718	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

jmunch-claude-code-setup: Instructions file for Claude Code