Borrowing it
Nothing to install: this file belongs to kaisers-io/refs. 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/kaisers-io/refs/main/CLAUDE.mdgit clone --depth 1 https://github.com/kaisers-io/refsWrote 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/kaisers-io/refs/claude-md)<a href="https://agentmods.dev/instructions/kaisers-io/refs/claude-md"><img src="https://agentmods.dev/badge/instructions/kaisers-io/refs/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/kaisers-io/refs/claude-md"><img src="https://agentmods.dev/badge/instructions/kaisers-io/refs/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.01338 | $0.01338 |
| Opus 5 | $0.00669 | $0.00669 |
| Sonnet 5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade B, and why
refs CLAUDE.md scanned grade B with 1 finding 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 yesterday.
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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
5. Run any command refs printed **verbatim** — the string it printed, not an argv you rebuilt from How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repository
AGENTS.md is a symlink to this file, so Claude Code and Codex read the same instructions.
Finish every PR with a real test
pnpm check passing is not evidence the feature works. Fixtures carry the shapes their author
thought of; real repositories carry the ones nobody did. Before marking a PR ready:
pnpm build— test the bundle atpackages/cli/bin/refs.mjs, not the TypeScript source.- Clone a real upstream repository from GitHub into a scratch directory.
- Drive the feature end to end against it with a scratch
REFS_HOME, using the same--jsonpath an agent uses. - Compare what refs reports against ground truth computed from git itself — e.g. package names
from
git ls-treeat both revisions, diffed. Report the comparison, not just the output. - Run any command refs printed verbatim — the string it printed, not an argv you rebuilt from
the same parts. A suggested command that does not execute is a bug, and rebuilding the argv
hides exactly the bugs that matter: a
<ref>placeholder passes straight through a hand-built array while a shell reads it as an input redirection. - Exercise the lifecycle:
remove, then confirm nothing is left (config, state, checkout, pruned parent directories, no orphans indoctor,resolveanswersunmatched_query), thenaddagain and confirm behaviour is unchanged.
To put a ref at a chosen point in history without fabricating anything, clone the real repository,
git checkout -B main <old-sha> in it, refs add from that file:// path with
REFS_ALLOW_FILE_URLS=1 so refs builds the config from real state, then advance the clone and
refs sync. The range is then real upstream history.
Why this is a rule: a feature once shipped with 988 green tests, including end-to-end ones against
file:// fixtures, and reported nothing at all on TanStack Query — two negation patterns in its
pnpm-workspace.yaml silenced every finding. No fixture used a negation pattern.
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.
- yesterday First seen · 99 lines · 1,338 tokens per session scan B 9121dd00fabb
refs CLAUDE.md is an instructions file published in the GitHub repository kaisers-io/refs (7 stars, last pushed 2d ago), licensed MIT. It adds 1,338 tokens to every session, about $0.0067 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.
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).
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.
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.