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 skills add eSlider/2dph --skill braingit clone --depth 1 https://github.com/eSlider/2dphWrote 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/skills/eslider/2dph/brain)<a href="https://agentmods.dev/skills/eslider/2dph/brain"><img src="https://agentmods.dev/badge/skills/eslider/2dph/brain/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/skills/eslider/2dph/brain"><img src="https://agentmods.dev/badge/skills/eslider/2dph/brain.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.00075 | $0.02454 |
| Opus 5.5 | $0.00030 | $0.00982 |
| Sonnet 5.5 | $0.00015 | $0.00491 |
| Haiku 4.5 | $0.00007 | $0.00245 |
Grade A, and why
brain 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 1mo 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brain — deduction over facts and info
One embedded Ladybug graph (var/kb.lbug, read-only when queried) holding two
roots:
- facts — assertions backed by ≥2 independent sources (docker ps × compose
× ssh-config × docs),
confidence: confirmed. - info — descriptive/narrative leafs, searchable, never asserted.
Search = deduction: facts root first, info root second, web-search as the
second independent source when local roots cannot confirm. An answer is
confirmed only if it comes off the facts root; anything else is
(not confirmed).
bin/brain/search.go "Matrix federation" # pointers + snippets, YAML
bin/brain/search.go "onlyoffice postgres" --root facts # restrict to confirmed
bin/brain/search.go "where is cs-lexicon" --json | yq '.[].ref'
bin/brain/search.go "who works where" --as-of 2025-01-01 # D24 intervals
bin/brain/add.go --text T --root facts --source "a.md x b.md"
bin/brain/get.go <id> --body # full chunk only when needed
bin/brain/stats.go # index health
bin/brain/eval.go # recall@5 >= 0.95 gate (Go, via Zig CGO)
--as-of YYYY-MM-DD keeps leafs whose valid_from/valid_to cover that day
(empty interval = always; not D16 source staleness).
Schema of a written leaf (source/external_id/observed_at/kind, dedup by
ContentHash, versioning): see docs/brain/contract.md (P-9.2/P-9.3); audit
compliance with bin/brain/audit-contract.go.
Read через контракт (клиент, P-9.5)
bin/brain/*.go выше читают kb.lbug напрямую (нужна локальная БД + cgo).
Для агентов/скриптов/gator/cv на любой машине с brain-сервисом (HTTP :8630,
bin/brain/serve.go) есть сервисный клиент read-контракта — тот же JSON,
без kb.lbug и без cgo:
bin/brain/client.go search "onlyoffice postgres" --root facts --json # факты: гейт facts
bin/brain/client.go search "onlyoffice postgres" # facts → info, info помечены (not confirmed)
bin/brain/client.go get <id> --body # полный текст + source (доказательства)
bin/brain/client.go stats --json
bin/brain/client.go audit # гигиена facts-корня (exit 1 при hypothesis/partial)
bin/brain/client.go search "q" --root facts --as-of 2025-01-01 # D24 валидность
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +94 lines b80a4bfdcc27
- 1mo ago First seen · 56 lines · 75 tokens per session scan A 5d1e5001ddc1
brain is a skill published in the GitHub repository eSlider/2dph (3 stars, last pushed 24d ago), licensed MIT. It adds 75 tokens to every session and 2,454 once invoked, about $0.0003 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 skills, from other repositories
engrama-onboard
Build a personalized Engrama memory graph for any user through a conversational interview. Use this skill whenever someone says "set up Engrama", "create my graph", "onboard", "build my profile", "configure Engrama for me", or asks how to start using Engrama. Also use when the user mentions they have a different role…
life-memory-mcp-connect
Set up an external AI agent to connect to the Life Memory System through MCP, including verified installation, retrieval, RawEvent writes, sync, diagnostics, and Working-Agent governance. Use when an agent needs to install or verify the Life Memory MCP bridge, onboard Codex/Claude/Cursor/Windsurf style clients, or…
life-memory-media-ingestion
Teach an external agent how to send links, files, images, tables, audio, and video into the Life Memory System as reviewable media note artifacts through MCP.
shodh-memory
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.
lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP). Use for ANY multi-step task where state should outlive one context window or span agents: long investigations, debugging sessions, audits, multi-agent searches, systematic explorations, planning with many interdependent constraints…