Borrowing it
Nothing to install: this file belongs to snow-wind-001/CodeRecoder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/snow-wind-001/CodeRecoder/main/AGENTS.mdgit clone --depth 1 https://github.com/snow-wind-001/CodeRecoderWrote 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/snow-wind-001/coderecoder/agents-md)<a href="https://agentmods.dev/instructions/snow-wind-001/coderecoder/agents-md"><img src="https://agentmods.dev/badge/instructions/snow-wind-001/coderecoder/agents-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.
<a href="https://agentmods.dev/instructions/snow-wind-001/coderecoder/agents-md"><img src="https://agentmods.dev/badge/instructions/snow-wind-001/coderecoder/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00543 | $0.00543 |
| Opus 5 | $0.00271 | $0.00271 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
CodeRecoder AGENTS.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 7d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/ contains the TypeScript MCP server. src/index.ts registers tools and transports; manager modules handle projects, snapshots, history, and analysis; shared contracts live in src/types.ts. Compiled output goes to ignored dist/. Integration tests are in test/, while test_mcp_json_fix.js is a focused root-level protocol check. Setup helpers and user documentation live at the repository root.
Build, Test, and Development Commands
npm installinstalls dependencies (Node 18+).npm run devruns the MCP server directly fromsrc/index.tswithtsx.npm run buildcompiles strict TypeScript intodist/.npm startstarts the compiled stdio server.npm run lintperforms a no-output TypeScript type check.npm run test:quickruns the short core snapshot workflow.npm testruns the full workflow;npm run test:jsexercises MCP tools over JSON-RPC.
Build before running integration tests. Tests require Linux shell utilities, write access to /tmp, and rsync for project snapshots.
Coding Style & Naming Conventions
Use two-space indentation, single-quoted strings, semicolons, and explicit types at public boundaries. Use PascalCase for classes and exported types, camelCase for functions and variables, and descriptive filenames such as projectSnapshotManager.ts. Retain .js suffixes in ESM imports. Send diagnostics to stderr (console.error); stdout is reserved for MCP JSON-RPC.
Testing Guidelines
Tests are end-to-end scripts; no coverage gate is configured. Name new workflows test_<behavior>.sh or test_<behavior>.js. Use isolated /tmp/coderecoder_* fixtures, clean them afterward, and validate responses and restored contents. Run npm run lint, npm run build, and the relevant workflow before submitting.
Commit & Pull Request Guidelines
History uses concise summaries, sometimes with Conventional Commit prefixes. Prefer focused, imperative messages such as fix: preserve snapshot chain on restore. Pull requests should explain the change, list verification commands, link issues, and call out MCP schema or configuration changes. Include terminal output for protocol changes; add screenshots only for visible output 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.
- 7d ago First seen · 34 lines · 543 tokens per session scan A 1a0b55b552a1
CodeRecoder AGENTS.md is an instructions file published in the GitHub repository snow-wind-001/CodeRecoder (2 stars, last pushed 2d ago), licensed MIT. It adds 543 tokens to every session, about $0.0027 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-09-05.
Other instructions, from other repositories
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).