Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/iikarus/dragon-brain/claude-mdgit clone --depth 1 https://github.com/iikarus/Dragon-BrainWrote 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/iikarus/dragon-brain/claude-md)<a href="https://agentmods.dev/instructions/iikarus/dragon-brain/claude-md"><img src="https://agentmods.dev/badge/instructions/iikarus/dragon-brain/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 | $0.06132 | $0.06132 |
| Opus 5 | $0.03066 | $0.03066 |
| Sonnet 5 | $0.01226 | $0.01226 |
| Haiku 4.5 | $0.00613 | $0.00613 |
Grade A, and why
Dragon-Brain 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 5d 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dragon Brain — CLAUDE.md
Drop this file into your project root or reference it from your Claude Code config to teach Claude how to use its persistent memory layer.
The Harness
Assertive pushback is non-negotiable. See global ~/.claude/CLAUDE.md § The Harness — 6 guardrails against yes-man behavior. Do NOT hedge-then-agree. Say NO first, make Tabish argue his case. Devil's advocate on every decision. Name the opportunity cost.
Audit Remediation (April–May 2026, Complete 2026-05-09)
4-phase adversarial audit found 83 contract violations across 37 source files. Fixes shipped in 10 batches B1–B10, all landed. Final state: violations 64 → 13 (~80% eliminated), remainder are documented legitimate fallback paths under quarterly review.
B10 — Async-Native Repository Migration (completed in 8 sub-batches B10.A through B10.epic-finalize):
- AsyncMemoryRepository wrapper (
asyncio.to_threadover FalkorDB sync client; ~75 call sites migrated across CrudMixin, SearchChannels, TemporalMixin, ValidationMixin, AnalysisMixin) - Cross-store compensation in
crud.pyfor create/update/delete entity — Qdrant upsert failure rolls back FalkorDB write to prevent split-brain orphans - Integration test harness via
testcontainers-pythonattests/integration/test_db_kill_scenarios.py— 5 tests using realcontainer.kill()to assert SearchError on infra outage - 1230 unit tests pass under
-W error, zero RuntimeWarning leakage - B10.5 (native async via
falkordb.asyncio.FalkorDB) deferred as future epic — currentasyncio.to_threadwrapper is a correct intermediate state; FalkorDB v1.4.0 ships native async support, future epic will swap the wrapper out - B10.F entity-level lock granularity deliberately deferred to a future epic — project-level locks remain in place, appropriate for current scale
The lie this audit closed
Before B1: search() wrapped its entire pipeline in except Exception: return []. The MCP search_memory tool transformed that into "No results found." — a confident string lie indistinguishable from "I genuinely have no memories on this topic." Every degraded memory query was Claude operating on missing context without knowing it. For two months, Dragon Brain was potentially lying to Claude on every infrastructure failure.
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.
- 5d ago First seen · 416 lines · 6,132 tokens per session scan A 0284bfbe5398
Dragon-Brain CLAUDE.md is an instructions file published in the GitHub repository iikarus/Dragon-Brain (50 stars, last pushed 13d ago), licensed MIT. It adds 6,132 tokens to every session, about $0.0307 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-30.
Other instructions, from other repositories
automem CLAUDE.md
Instructions for verygoodplugins/automem, covering claude.md, project overview, development commands, setup environment and development.
remnic AGENTS.md
AGENTS.md instructions for joshuaswarren/remnic, covering remnic - agent guide, architecture boundaries (non-negotiable), upstream references, adapter implementation rules and openclaw compatibility window.
sibyl CLAUDE.md
Claude Code instructions for hyperb1iss/sibyl, covering sibyl development guide, project overview, sibyl integration, always use skills and research → do → reflect cycle.
brainlayer AGENTS.md
Instructions for EtanHey/brainlayer, covering brainlayer — a letter from etan, brainlayer agent notes (operational), review guidelines, key paths and database.
superlocalmemory copilot-instructions.md
Copilot instructions for qualixar/superlocalmemory, covering superlocalmemory (slm) — agent rules, session start, remember, recall and optimize (fail-open).
dakera-cli CLAUDE.md
Instructions for Dakera-AI/dakera-cli, covering dakera-cli, key commands, architecture and conventions.