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.
npx agentmods add instructions/czottmann/render-claude-context/claude-mdgit clone --depth 1 https://github.com/czottmann/render-claude-contextWrote 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.
[](https://agentmods.dev/instructions/czottmann/render-claude-context/claude-md)<a href="https://agentmods.dev/instructions/czottmann/render-claude-context/claude-md"><img src="https://agentmods.dev/badge/instructions/czottmann/render-claude-context/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.00658 | $0.00658 |
| Opus 5 | $0.00329 | $0.00329 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
render-claude-context 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Node.js CLI tool that processes CLAUDE.md files with a hierarchical collection system. The tool walks up the directory tree from the current working directory to the user's home folder, collecting all CLAUDE.md files and processing them with file import resolution.
Key Files
- Main Entry Point:
index.js- CLI tool implementation with shebang for direct execution - Configuration:
package.json- Package configuration with bin entry for global installation - Specification:
SPEC.md- Complete project requirements and behavior specification - Documentation:
docs/- Comprehensive documentation for development and usage
Core Architecture
File Processing System (index.js:7-30)
- File Discovery:
collectClaudeFiles()walks up directory tree from current location to~ - Import Resolution:
resolveImports()processes@imports with tilde expansion support - Recursive Processing: Imported files can contain their own imports, creating dependency chains
- Output Generation: Outputs processed content in reverse order with HTML comment separators
Import Syntax (index.js:32-67)
- Format:
@followed immediately by a file path - Tilde expansion:
~/pathresolves to home directory (index.js:42-46) - Path resolution: Relative to the file containing the import statement
- Non-file paths after
@are left unchanged - Circular import protection via Set tracking (index.js:35)
Output Format (index.js:87-107)
- Files processed in reverse collection order
- Each file separated by HTML comments containing file paths:
<!-- /path/to/file --> - No duplicate file names in output
~/.claude/CLAUDE.mdappears first in output
Development Commands
Run the tool: node index.js
Install globally: npm install -g . then use claude-static-context-dump
Test import resolution: Check output for resolved @ imports vs literal text
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.
- 3d ago First seen · 66 lines · 658 tokens per session scan A 20a4b9186ca6
render-claude-context CLAUDE.md is an instructions file published in the GitHub repository czottmann/render-claude-context (15 stars, last pushed 1y ago), licensed MIT. It adds 658 tokens to every session, about $0.0033 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-30.
Other instructions, from other repositories
antigravity-claude-proxy CLAUDE.md
Instructions for badrisnarayanan/antigravity-claude-proxy, covering claude.md, commands and non-obvious things.
ccproxy AGENTS.md
AGENTS.md instructions for starbaser/ccproxy, covering claude.md, project overview, cross-project documentation — first-party stack, commands and cli.
ccproxy CLAUDE.md
Claude Code instructions for starbaser/ccproxy, a project described as: Build mods for Claude Code: Hook any request, modify any response, /model "with-your-custom-model", intelligent model routing using your logic or ours.
gemini-rules-repo GEMINI.md
Instructions for sanpicule/gemini-rules-repo, covering gemini 開発ルール, 1. コミットメッセージ, 2. セキュリティ, 3. ブランチモデル and ブランチの種類.
desmond CLAUDE.md
Claude Code instructions for llegomark/desmond, covering claude.md, project overview, development commands, essential commands and build notes.
awesome-gemini GEMINI.md
Instructions for aaronhuff/awesome-gemini, covering welcome to the gemini documentation, introduction to gemini, getting started, project structure and gems.