Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add toroleapinc/claude-brain/plugin install claude-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/skills/toroleapinc/claude-brain/brain-conflicts)<a href="https://agentmods.dev/skills/toroleapinc/claude-brain/brain-conflicts"><img src="https://agentmods.dev/badge/skills/toroleapinc/claude-brain/brain-conflicts.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.00012 | $0.00316 |
| Opus 5 | $0.00006 | $0.00158 |
| Sonnet 5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade B, and why
brain-conflicts scanned grade B 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/brain-conflicts.json 2>/dev/null || echo '{"conflicts":[]}' What it actually says
The user wants to resolve pending brain merge conflicts.
Steps
-
Read the conflicts file:
cat ~/.claude/brain-conflicts.json 2>/dev/null || echo '{"conflicts":[]}' -
Filter to unresolved conflicts (where
resolvedis nottrue). -
If no unresolved conflicts, tell the user: "No pending conflicts. Brain is fully synced."
-
For each unresolved conflict, present:
- The topic
- What Machine A says
- What Machine B says
- The AI's suggestion and confidence level
Ask the user to choose:
- Accept AI suggestion: Apply the suggestion
- Keep Machine A's version: Use A's content
- Keep Machine B's version: Use B's content
- Keep both (machine-specific): Tag each with its machine name
- Custom: Let the user type their own resolution
-
After each resolution:
- Mark the conflict as
resolved: truewith the chosen resolution in brain-conflicts.json - Apply the resolution to the appropriate brain file (CLAUDE.md, memory, etc.)
- Mark the conflict as
-
After all conflicts are resolved:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/push.sh" -
Show summary: "X conflicts resolved. Brain is now fully synced."
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.
- 6d ago First seen · 43 lines · 12 tokens per session scan B 8decf5296d92
brain-conflicts is a skill published in the GitHub repository toroleapinc/claude-brain (85 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 316 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
alive:capture-context
Use when external content arrives in the session — emails, transcripts, screenshots, documents, files, or in-session research worth keeping. Also use when there's nothing obvious to capture — the skill checks 03Inbox/ for unrouted files and enters inbox scan mode. Stores raw content, routes to bundles, extracts tasks…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:load-context
The human mentions a walnut to work on, asks about a specific venture/experiment/project, or wants to check status — not just explicit 'load X'. Load the brief pack (3 files), resolve the people involved, check the active bundle — then surface one observation and ask what to work on. Context loads in tiers: walnut and…
alive:mine-for-context
Deep context extraction from source material. Creates reference bundles, builds extraction plans, tracks what's been extracted, and discovers new targets — people, subjects, patterns, connections. The archaeologist that turns raw sources into structured knowledge. Can be invoked by alive:session-history for targeted…
alive:my-context-graph
Render an interactive map of your world. Generates the world index from all walnut and bundle frontmatter, then produces a force-directed graph showing connections between walnuts, people, bundles, and tags. Opens in the browser.