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/stevemolitor/claude-code.el/claude-mdgit clone --depth 1 https://github.com/stevemolitor/claude-code.elWhat 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.00377 | $0.00377 |
| Opus 5 | $0.00188 | $0.00188 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
claude-code.el 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.
What it actually says
Claude Code Development Guide
Build and Test Commands
- Install package:
M-x package-install-file RET /path/to/claude-code.el - Use project Makefile targets (preferred methods):
- Byte compile:
make compile - Lint with checkdoc:
make checkdoc - Run both checkdoc and compile:
make all
- Byte compile:
- Alternative direct commands:
- Byte compile:
emacs -Q --batch -f batch-byte-compile claude-code.el - Check package:
emacs -Q --batch -l package-lint.el -f package-lint-batch-and-exit claude-code.el - Lint with checkdoc:
emacs -Q --batch -l checkdoc -f checkdoc-file claude-code.el
- Byte compile:
Code Style Guidelines
- Prefix all functions/variables with
claude-code-(public) orclaude-code--(private) - Follow standard Emacs Lisp naming conventions (kebab-case)
- Use lexical binding (include
lexical-binding: tin header) - Organize with section headers:
;;;; Section Name - Maintain proper package headers and autoload declarations
- Docstring for all functions and variables
- Add a blank line after the first line of docstrings for multi-line descriptions
- First line should be a complete sentence ending with a period
- Maintain dependency requirements: Emacs 30.1+, transient 0.4.0+, eat 0.8+
Error Handling
- Use
if-letfor conditional execution with potential null values - Provide clear error messages with
errorfunction - Check for running Claude instance before sending commands
Project Structure
- Single file package with clear module organization
- Licensed under Apache License 2.0
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 · 32 lines · 377 tokens per session scan A 7d755f8eb7ea
claude-code.el CLAUDE.md is an instructions file published in the GitHub repository stevemolitor/claude-code.el (743 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 377 tokens to every session, about $0.0019 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.