Borrowing it
Nothing to install: this file belongs to svyatov/handrail. 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/svyatov/handrail/main/CLAUDE.mdgit clone --depth 1 https://github.com/svyatov/handrailWrote 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/svyatov/handrail/claude-md)<a href="https://agentmods.dev/instructions/svyatov/handrail/claude-md"><img src="https://agentmods.dev/badge/instructions/svyatov/handrail/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.1 | $0.00390 | $0.00390 |
| Opus 5 | $0.00195 | $0.00195 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
handrail 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 6d 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.
What it actually says
handrail
docs/spec.md is the behavioural source of truth. CONTEXT.md defines the vocabulary.
Commands
task test # go test -race -shuffle=on ./...
task cover # the same run with coverage, fails under 95%
task lint # golangci-lint run, then fmt --diff
task build # the release build
CI calls these same tasks, so a local pass means what a green check means.
Two constraints the build enforces
- Zero third-party runtime dependencies.
depguardallows only the stdlib and this module outside_test.go;github.com/rogpeppe/go-internalis the sole test-only one. os.Exitonly inmain.go, sorun()returns an exit code and stays testable.forbidigoenforces it.
Tests
testscript over the compiled binary is the primary seam: a new case goes in
testdata/script/*.txtar, not a new _test.go. Unit tests under internal/ are only
for what a process boundary cannot produce. See docs/adr/0009-testing-strategy.md.
Agent skills
Issue tracker
Issues live as GitHub issues in svyatov/handrail, managed via the gh CLI. See docs/agents/issue-tracker.md.
Triage labels
The five canonical roles, each label string equal to its name. See docs/agents/triage-labels.md.
Domain docs
Single-context: CONTEXT.md + docs/adr/ at the repo root. See docs/agents/domain.md.
Semantic code navigation
Serena's LSP symbol tools, optional, needs gopls. See docs/agents/serena.md.
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.
- 6d ago First seen · 46 lines · 390 tokens per session scan A 4263bdac069f
handrail CLAUDE.md is an instructions file published in the GitHub repository svyatov/handrail (2 stars, last pushed 3d ago), licensed MIT. It adds 390 tokens to every session, about $0.0019 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
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).
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).
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.
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.