Borrowing it
Nothing to install: this file belongs to rhi-zone/normalize. 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/rhi-zone/normalize/master/CLAUDE.mdgit clone --depth 1 https://github.com/rhi-zone/normalizeWrote 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/rhi-zone/normalize/claude-md)<a href="https://agentmods.dev/instructions/rhi-zone/normalize/claude-md"><img src="https://agentmods.dev/badge/instructions/rhi-zone/normalize/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/rhi-zone/normalize/claude-md"><img src="https://agentmods.dev/badge/instructions/rhi-zone/normalize/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.07124 | $0.07124 |
| Opus 5.5 | $0.02850 | $0.02850 |
| Sonnet 5.5 | $0.01425 | $0.01425 |
| Haiku 4.5 | $0.00712 | $0.00712 |
Grade C, and why
normalize CLAUDE.md scanned grade C with 2 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 2mo 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
**installer URL:** `curl -fsSL https://rhi.zone/normalize/install.sh | sh` — the canonical copy lives at `https://github.com/rhi-zone/rhi.zone/blob/master/normalize/install.sh`; the in-repo `install.sh` is just a synced Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**installer URL:** `curl -fsSL https://rhi.zone/normalize/install.sh | sh` — the canonical copy lives at `https://github.com/rhi-zone/rhi.zone/blob/master/normalize/install.sh`; the in-repo `install.sh` is just a synced How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
behavioral rules for me in this repo.
stuff to go read when it's relevant: docs/philosophy.md (design tenets), docs/architecture-decisions.md (technical choices), docs/cli-design.md (CLI surface + principles), docs/audit-2026-03-12.md (architecture audit w/ action items).
publishing
it's published on crates.io as 49 crates (+4 publish = false ones: normalize-grammars, normalize-semantic-facts, xtask, benches). all at v0.3.2 rn (early, still actively being built).
installer URL: curl -fsSL https://rhi.zone/normalize/install.sh | sh — the canonical copy lives at https://github.com/rhi-zone/rhi.zone/blob/master/normalize/install.sh; the in-repo install.sh is just a synced copy of it.
API-first
normalize IS an API that happens to have a CLI on top of it. the service layer returns typed data, the CLI just renders it. so when i'm designing a command i start with the data model — what shape does the result actually have? the CLI surface (subcommand name, flags, positional layout) follows from THAT. i never let how it looks in a terminal drive the data shape.
what that means in practice:
- a command that returns a list of items returns
Vec<T>(or a wrapper), no matter whether the input was a flag, a glob, or a subcommand name. --json/--jq/--jsonlare first-class on every command, bc programmatic consumers (agents, scripts, LSP) are primary users, not an afterthought.- when designing a report struct, the question is "what does whoever's calling this API want to DO with the result?" — never "what should this look like printed in a terminal?"
architecture
crate-level context lives in docs/crates.md — that's the canonical registry of every workspace crate (purpose, category, namespace ownership). it replaced the old per-directory SUMMARY.md thing at the crate level. the actually-maintainable source of truth for a crate's purpose is its Cargo.toml description field — keep THAT accurate and the registry stays cheap to regenerate. check the registry before asking "wait which crate owns X?"
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.
- 2mo ago First seen · 183 lines · 7,124 tokens per session scan C 4fed3d65acb1
normalize CLAUDE.md is an instructions file published in the GitHub repository rhi-zone/normalize (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 7,124 tokens to every session, about $0.0285 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.