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/btn0s/redline/claude-mdgit clone --depth 1 https://github.com/btn0s/redlineWrote 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/btn0s/redline/claude-md)<a href="https://agentmods.dev/instructions/btn0s/redline/claude-md"><img src="https://agentmods.dev/badge/instructions/btn0s/redline/claude-md.svg" alt="Measured on agentmods" 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 | $0.01754 | $0.01754 |
| Opus 5 | $0.00877 | $0.00877 |
| Sonnet 5 | $0.00351 | $0.00351 |
| Haiku 4.5 | $0.00175 | $0.00175 |
Grade A, and why
redline 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude / coding agents working on this repo.
What this is
@btn0s/redline — a local-first review tool for markdown files. Spin it up
on a .md file (npx @btn0s/redline ./plan.md), get a Google-Docs-style
commenting UI on the rendered markdown, and copy all threads back out as
structured text to feed back into an LLM.
The intended primary use case is reviewing LLM-generated plans/specs.
Layout
cli/ Node CLI (entry: cli/index.ts → cli/server.ts)
plugins/ Vite dev plugin that mounts the same /api/file handlers
shared/ API handler helpers shared between dev plugin and CLI
src/ React + Vite SPA (the review UI)
components/ App components (review-header, comment-sidebar, editor, dialogs, etc.)
ui/ shadcn-ish primitives (don't hand-edit unless necessary)
contexts/ CommentContext, ShortcutSchemeContext, ThemeProvider
extensions/ Tiptap extensions (CommentMark, CommentShortcuts)
hooks/ useFile, useComments, useEditorCommentSync, useCommentSidebarLayout, ...
lib/ Pure utilities (comment-anchoring, format-shortcut, mod-key, utils)
types/ Shared TS types (Comment)
index.css Theme tokens + .tiptap document styles + redline annotation styles
scripts/build-cli.js esbuild bundle for the CLI
skills/redline/ Agent skill shipped with the package
docs/specs/ Design specs / plans (sometimes referenced from prompts)
The dev experience and the production CLI talk to the same /api/file
contract. Keep plugins/review-md-dev-api.ts and cli/server.ts in sync,
and prefer pushing logic into shared/api-handlers.ts so both code paths
get it for free.
Commands
pnpm dev # vite dev server (set REVIEW_MD_FILE=path/to/foo.md in .env.local for the dev API)
pnpm build # tsc -b && vite build && bundle CLI into dist/cli/index.js
pnpm typecheck # tsc -b
pnpm lint # eslint .
pnpm format # prettier --write **/*.{ts,tsx}
pnpm redline # build + run dist/cli/index.js (smoke-test the published binary)
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 · 147 lines · 1,754 tokens per session scan A 01d274e2892c
redline CLAUDE.md is an instructions file published in the GitHub repository btn0s/redline (5 stars, last pushed 3mo ago), licensed MIT. It adds 1,754 tokens to every session, about $0.0088 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
ai-dial-core CLAUDE.md
Claude Code instructions for epam/ai-dial-core, covering claude.md, build & run, set credentials via environment variables, build (skip tests) and run all tests.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).