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/snow-wind-001/coderecoder/claude-mdgit clone --depth 1 https://github.com/snow-wind-001/CodeRecoderWhat 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.01220 | $0.01220 |
| Opus 5 | $0.00610 | $0.00610 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
CodeRecoder 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.
How it starts
The opening of the file, as written. The whole thing — 116 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.
CodeRecoder Architecture
CodeRecoder is an AI-enhanced code version management system built on the Model Context Protocol (MCP). It provides instant file snapshots, project-level version control, and smart change detection, similar to Cursor's multi-round generation and rollback features.
Core Design Principles
-
Manager-Based Architecture: Each major function (file snapshots, project snapshots, history tracking, project activation) is handled by a dedicated manager class in
src/:ProjectManager- Global project workspace management and activationFileSnapshotManager- High-performance file-level snapshots via direct file copyingProjectSnapshotManager- Cursor-style project snapshots with incremental/full strategiesHistoryManager- Traditional edit history tracking (legacy support)DataStructureManager- Project directory structure and configurationAIAnalysisService- Serena integration for code analysis
-
Project-Isolated Data: Each activated project maintains its own
.CodeRecoder/directory containing:config/- Project settings and metadatasnapshots/files/- File-level snapshots organized by sessionsnapshots/projects/- Complete project snapshotshistory/- Edit history recordsanalysis/- AI-generated insightslogs/- Debug and error logs
-
Direct File Copying: File snapshots use direct file system copying (not content parsing) for sub-50ms performance. This means snapshot operations don't parse file contents.
-
Four-Way Change Detection: Project snapshots use intelligent detection:
- Git status changes
- File stat comparison (size, mtime)
- Content SHA256 hashing
- Timestamp-based recent file scanning
-
Incremental + Full Snapshot Strategy: Project snapshots can be incremental (only changed files) or full (all files). Incremental snapshots maintain dependency chains for complete restoration.
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 · 116 lines · 1,220 tokens per session scan A 26472416ffea
CodeRecoder CLAUDE.md is an instructions file published in the GitHub repository snow-wind-001/CodeRecoder (1 stars, last pushed 8mo ago), licensed MIT. It adds 1,220 tokens to every session, about $0.0061 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.
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.