Borrowing it
Nothing to install: this file belongs to inth3shadows/runecho. 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/inth3shadows/runecho/master/CLAUDE.mdgit clone --depth 1 https://github.com/inth3shadows/runechoWrote 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/inth3shadows/runecho/claude-md)<a href="https://agentmods.dev/instructions/inth3shadows/runecho/claude-md"><img src="https://agentmods.dev/badge/instructions/inth3shadows/runecho/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/inth3shadows/runecho/claude-md"><img src="https://agentmods.dev/badge/instructions/inth3shadows/runecho/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.01207 | $0.01207 |
| Opus 5.5 | $0.00483 | $0.00483 |
| Sonnet 5.5 | $0.00241 | $0.00241 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
runecho 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 27d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RunEcho Workflow
- This repo uses RunEcho as the code-truth source for symbol existence and structural drift questions.
- Use the
runechoMCP server before making claims about what functions, classes, exports, or imports exist. - If RunEcho reports stale or missing baseline data, run
runecho-ir repo reindex <name>before trusting structural answers. - Treat unresolved-symbol findings from
runecho-guardas verification stops until they are fixed or intentionally explained.
Release Tags
- Release tags must be monotonic (
vX.Y.Z, semver-increasing) — non-monotonic tags previously brokegit describe/version stamping (issue #51). - Enforced by a
pre-pushhook that rejects a tag push that isn't semver-greater than the highest existing tag. Tracked source:githooks/pre-push. Not auto-installed by git — runbash install.sh --hook-pre-pushfrom the repo root on each machine/worktree setup that pushes tags (installs into$(git rev-parse --git-common-dir)/hooks/pre-push).
Git hooks — there are five, from two different installers
Both installers write into $(git rev-parse --git-common-dir)/hooks, which is
shared across every worktree of this repo. Knowing which installer owns a hook
matters: a change that overwrites one silently disables the other's feature.
Since #443 installHooks owns only a # >>> runecho >>> … # <<< runecho <<<
block in each of its four hooks (cmd/runecho-ir/hookblock.go), inserted after
the shebang and replaced in place, so other tools' content in the same file
(kb-mcp's kb-drift block) survives a reinstall. Blocks never exec or exit
early except to propagate a guard failure; legacy unmarked runecho hooks are
migrated once; malformed markers are refused with the file left untouched.
| Hook | Installed by | Does |
|---|---|---|
pre-commit |
runecho-ir install → installHooks (cmd/runecho-ir/install.go) |
runs runecho-guard at commit time |
post-commit |
same | background runecho-ir repo reindex . |
post-merge |
same | version-check --quiet (freshness advisory — never builds), then background runecho-ir repo reindex . |
post-checkout |
same, on branch switches only ($3 == 1) |
version-check --quiet (advisory), then background runecho-ir repo reindex . |
pre-push |
bash install.sh --hook-pre-push (githooks/pre-push) |
rejects a non-monotonic vX.Y.Z tag push |
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.
- 27d ago Changed · +7 lines · +120 tokens per session 5c042f74110f
- 1mo ago Changed · -2 lines · +64 tokens per session ec212ba2f430
- 2mo ago First seen · 59 lines · 1,023 tokens per session scan A 4215034915e0
runecho CLAUDE.md is an instructions file published in the GitHub repository inth3shadows/runecho (2 stars, last pushed yesterday), licensed MIT. It adds 1,207 tokens to every session, about $0.0048 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.