Borrowing it
Nothing to install: this file belongs to hamchowderr/braynee. 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/hamchowderr/braynee/main/CLAUDE.mdgit clone --depth 1 https://github.com/hamchowderr/brayneeWrote 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/hamchowderr/braynee/claude-md)<a href="https://agentmods.dev/instructions/hamchowderr/braynee/claude-md"><img src="https://agentmods.dev/badge/instructions/hamchowderr/braynee/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/hamchowderr/braynee/claude-md"><img src="https://agentmods.dev/badge/instructions/hamchowderr/braynee/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.01925 | $0.01925 |
| Opus 5.5 | $0.00770 | $0.00770 |
| Sonnet 5.5 | $0.00385 | $0.00385 |
| Haiku 4.5 | $0.00193 | $0.00193 |
Grade A, and why
braynee 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 16d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
braynee — project instructions
braynee is an Obsidian second-brain Claude Code plugin (TypeScript/Node, hooks +
skills + agents). It is installed as a local CC plugin; the live install runs from
~/.claude/plugins/cache/braynee/braynee/<version>/, the source is this repo.
Hooks: never gate with the if field — self-gate in JS
The Claude Code hook if field (permission-rule syntax like
"if": "Bash(bd create *) || Bash(bd close *)") is version-unreliable and must
not be used. Verified live on 2026-05-24 (cp-068):
- CC 2.1.143: any
if-bearing hook never fires — even a single-pattern"if": "Bash(bd *)". This silently broke the three-way task mirror (beads-todo-remindernever emitted its reminder) and would disable the no-push-to-main guard. - Older CC: the
iffield is ignored, so the hook fires on every Bash command (and duplicated registrations fire N times).
Rule: register Bash hooks with only "matcher": "Bash" (no if) and gate
inside the hook's JS — match the command with a regex and process.exit(0) early
on a non-match, before any side effect. Every gated hook here already does this
(beads-todo-reminder, beads-status-sync, commit-cadence-nudge,
beads-claim-to-branch, beads-dashboard-refresh,
check-no-main-push, branch-name-check).
Testing hooks — two layers
Hook bugs split into "JS logic" and "the CC↔hooks.json boundary" (firing,
additionalContext delivery). The boundary class is invisible to any test that
pipes synthetic stdin into a hook — that's how the if-field bug shipped. So use
both layers:
1. Headless assertions — bin/braynee-self-test (CI)
node bin/braynee-self-test runs in CI (Ubuntu/macOS/Windows, Node 20/22).
Section 8 ("Gated-hook output assertions") feeds matching and non-matching command
JSON to each gated hook and asserts emit on a match, silence on a non-match —
locking the self-gating contract above. Add an assertion here whenever you add or
change a gated hook. Catches JS/regex regressions; does not exercise CC.
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.
- 16d ago Changed · -8 tokens per session 7bc7d42bfd99
- 1mo ago First seen · 133 lines · 1,933 tokens per session scan A c912dce97cc9
braynee CLAUDE.md is an instructions file published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 5d ago), licensed MIT. It adds 1,925 tokens to every session, about $0.0077 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.