Borrowing it
Nothing to install: this file belongs to alcor6502/codifier-mcp. 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/alcor6502/codifier-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/alcor6502/codifier-mcpWrote 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/alcor6502/codifier-mcp/claude-md)<a href="https://agentmods.dev/instructions/alcor6502/codifier-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/alcor6502/codifier-mcp/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.
<a href="https://agentmods.dev/instructions/alcor6502/codifier-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/alcor6502/codifier-mcp/claude-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.02064 | $0.02064 |
| Opus 5.5 | $0.00826 | $0.00826 |
| Sonnet 5.5 | $0.00413 | $0.00413 |
| Haiku 4.5 | $0.00206 | $0.00206 |
Grade A, and why
codifier-mcp 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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codifier-mcp — working notes for Claude Code
Rule registry over SQLite, served as an MCP server. Twin of archivist-mcp;
both pin mcp-common-engine to a tag. Two servers in one process — the MCP
surface (server.py) and the admin page (web.py) — over one engine
(rules.py), because two processes on one SQLite database do not share the lock
that makes a multi-statement transaction atomic.
English in this repo: code, docstrings, errors, README, commit messages, tags.
Before you touch anything
VERSIONlives inrules.py, notserver.py. The engine is what the suites import; the server imports the engine. A grep againstserver.pyfinds nothing and reads like "no version".- A number is never written twice. Versions, counts, caps: read them from the
constant or count them. Where a copy is unavoidable, a check must compare the
two —
test_surface.pyis full of them. - One change at a time, in the working tree too. The bill comes at commit: two changes already mixed in the same files cannot be separated afterwards.
git addnamed files. Never-A. Readgit status --shortline by line and ask whether each one is yours; a line you do not recognise is not.
Running the suites, and shipping
scripts/test.sh # the bench and the five suites, in order
scripts/ship.sh <msg-file> <file>... # suites, commit, push to main, release link
test.sh makes a venv, installs the engine from the pin in
requirements.txt — the tarball, or a clone of the same tag when the network
refuses the tarball — and runs the suites the CI runs, in the same order,
stopping at the first red. Each suite goes to a file and the script prints
exit=. test_surface.py reads both files and goes red if the suite list
differs from build.yml in either direction, or if the script carries a copy
of the tag.
ship.sh runs test.sh, git adds the named files, commits with the
anonymous identity passed on the command, pushes HEAD:refs/heads/main, proves
the push against the fetched hash, and — if VERSION moved in that commit —
prints the pre-filled release link. The tag is never typed and never pushed:
from the sandbox a tag push answers 403, and one typed on a tablet came out
V7.0.0, which the workflow's glob ignored in silence.
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.
- 1mo ago Changed · +24 lines · +333 tokens per session 3c5c7c413c10
- 1mo ago First seen · 129 lines · 1,731 tokens per session scan A 2dc1f96d1898
codifier-mcp CLAUDE.md is an instructions file published in the GitHub repository alcor6502/codifier-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 2,064 tokens to every session, about $0.0083 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.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.