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 skills/devvgwardo/brain-mcp/brain-memory-banknpx skills add DevvGwardo/brain-mcp --skill brain-memory-bankgit clone --depth 1 https://github.com/DevvGwardo/brain-mcpWrote 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/devvgwardo/brain-mcp/brain-memory-bank)<a href="https://agentmods.dev/skills/devvgwardo/brain-mcp/brain-memory-bank"><img src="https://agentmods.dev/badge/skills/devvgwardo/brain-mcp/brain-memory-bank.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.1 | $0.00000 | $0.01192 |
| Opus 5 | $0.00000 | $0.00596 |
| Sonnet 5 | $0.00000 | $0.00238 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
brain-memory-bank 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain Memory Bank
GSD-inspired persistent context pattern for brain-mcp multi-agent workflows.
Use when: Using brain-mcp to coordinate multiple subagents that need shared context across tasks.
What it solves: Subagents have no memory between tasks. This makes the orchestrator the memory bank using a single STATE.md file.
Pattern
Orchestrator
│
│ MAINTAINS: ~/.hermes/.brain/STATE.md
│
│ PER TASK:
│ 1. brain_set("task_context", $SLICE_OF_STATE)
│ 2. brain_wake(agent, goal + context)
│
│ AFTER RESULTS:
│ 1. brain_read() — collect agent posts
│ 2. Update STATE.md — "What Was Done", "Agent Context"
│ 3. brain_set next wave or end
│
└── Subagents: read brain_get("task_context"), do work, brain_post() results
Orchestrator Workflow
1. Initialize Session
BRAIN_STATE="$HOME/.hermes/.brain/STATE.md"
mkdir -p "$(dirname "$BRAIN_STATE")"
cat > "$BRAIN_STATE" <<'EOF'
# Brain MCP — Session State
## Session
Project: [project-name]
Session ID: [session-id]
Started: [YYYY-MM-DD HH:MM]
Status: active
## Current Phase
Phase: init
Updated: [YYYY-MM-DD HH:MM]
## Orchestrator Memory
### What Was Done
- (empty — fill after first wave)
### Active Decisions
- (empty)
### Blockers
- (none)
### Pending Results
- (none)
## Agent Context
## Files Under Work
## Session Log
EOF
2. Per-Wave: Inject Context Slices
Before brain_wake, extract relevant slice from STATE.md:
# Extract context relevant to this task
get_context_slice() {
local phase="$1" # e.g., "auth", "api", "frontend"
local state="$HOME/.hermes/.brain/STATE.md"
# Get orchestrator memory (always relevant)
echo "## Orchestrator Memory"
grep -A 20 "## Orchestrator Memory" "$state" 2>/dev/null || echo "(no memory yet)"
# Get relevant files under work
echo ""
echo "## Files Under Work (relevant to: $phase)"
grep -A 10 "## Files Under Work" "$state" 2>/dev/null | grep -i "$phase" || echo "(none)"
# Get agent context for relevant agents
echo ""
echo "## Agent Context"
grep -A 8 "### agent-" "$state" 2>/dev/null | grep -A 8 "$phase" || echo "(none)"
}
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 · 192 lines · 0 tokens per session scan A ab558712c749
brain-memory-bank is a skill published in the GitHub repository DevvGwardo/brain-mcp (8 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,192 tokens. 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…