Borrowing it
Nothing to install: this file belongs to jaemk/mind. 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/jaemk/mind/main/CLAUDE.mdgit clone --depth 1 https://github.com/jaemk/mindWrote 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/jaemk/mind/claude-md)<a href="https://agentmods.dev/instructions/jaemk/mind/claude-md"><img src="https://agentmods.dev/badge/instructions/jaemk/mind/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/jaemk/mind/claude-md"><img src="https://agentmods.dev/badge/instructions/jaemk/mind/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.04949 | $0.04949 |
| Opus 5.5 | $0.01980 | $0.01980 |
| Sonnet 5.5 | $0.00990 | $0.00990 |
| Haiku 4.5 | $0.00495 | $0.00495 |
Grade A, and why
mind CLAUDE.md scanned grade A 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`PATH` (see the fake `curl`/`gh` tests in `src/selfupdate.rs`). How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mind
A manager for agent tooling (skills, agents, rules, commands, workflows, tools, resources) that melds with
arbitrary git repos and links installed items into one or more agent homes
(default ~/.claude; see Paths::agent_homes). A tool or resource is
store-only: it is referenced by other items, not linked into an agent home.
The behavioral spec lives in spec/ and is the reference to verify
against. Each statement there has a stable ID (e.g. LIFE-4); tests cite the IDs
they cover in // spec: ID comments. Keep the spec and the implementation in
step: when behavior changes, update the spec doc and the citing tests in the same
change.
tests/spec_coverage.rs is a coverage gate run by cargo test (and CI): it
fails when a defined spec ID is neither cited by a test nor listed in its
ALLOWLIST, and when a test cites an ID that the spec does not define. So a new
spec ID forces a coverage decision - add a citing test or an allowlist entry with
a reason - and a test cannot cite an undocumented behavior. Only citations in
test code count: everything under tests/, plus the #[cfg(test)] regions of
src/. A // spec: comment on production code documents the implementation
site and is fine to write, but it asserts nothing, so it does not satisfy the
gate. CI is
.github/workflows/ci.yml (runs make ci: fmt-check + clippy + test). Locally,
use make ci-local (alias: make check): it runs the same clippy + test gate
but formats in place (cargo fmt) instead of fmt-check, so one command both
fixes formatting and runs the full gate. Prefer make ci-local over chaining
cargo fmt and make ci.
The toolchain is pinned in rust-toolchain.toml, so make ci-local and make ci lint with the same clippy. Do not bump it casually: a newer clippy adds
lints, -D warnings makes each one a hard error, and the new errors usually
land on code the bump does not touch. To bump, change channel there, update
the matching toolchain: inputs in .github/workflows/{ci,release,canary}.yml,
and run make ci-local. The jobs that build against a different toolchain on
purpose (the MSRV check, the release build, the crates.io publish) set
RUSTUP_TOOLCHAIN, which outranks the file; leave that in place or those gates
quietly start testing the wrong compiler.
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.
- 2d ago Changed · +40 tokens per session baca40c2e2f9
- 9d ago Changed · +15 tokens per session 6e38180e38a4
- 14d ago Changed · +3 lines · +124 tokens per session 8de317c98c1f
- 29d ago Changed · +3 lines · +108 tokens per session 8ac186046c8b
- 1mo ago Changed · +2 lines · +116 tokens per session f5dde910463a
- 1mo ago Changed · +7 lines · +137 tokens per session 4c2c5bfa3d05
- 2mo ago First seen · 279 lines · 4,409 tokens per session scan A 35dd407f6ce8
mind CLAUDE.md is an instructions file published in the GitHub repository jaemk/mind (1 stars, last pushed 2d ago), licensed MIT. It adds 4,949 tokens to every session, about $0.0198 per session on Opus 5.5. A static security scan graded it A with 1 finding (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).
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.