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/jame581/logseqbrain/brain-loadnpx skills add jame581/LogseqBrain --skill brain-loadgit clone --depth 1 https://github.com/jame581/LogseqBrainWhat 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.00096 | $0.04232 |
| Opus 5 | $0.00048 | $0.02116 |
| Sonnet 5 | $0.00019 | $0.00846 |
| Haiku 4.5 | $0.00010 | $0.00423 |
Grade A, and why
brain-load 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 3d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain Load
Read project context from the Claude Brain Logseq graph and present it to Claude so work can continue seamlessly across sessions and devices.
Prerequisites
Resolve the graph path per skills/_shared/path-resolution.md.
Loading a Specific Project
When the user says "load " or similar:
-
Find the project page using the algorithm in
references/matching.md. -
Read the digest — one Read.
Read(page, offset 0, limit 20)captures the page-top property block and the whole## Digest(seeskills/_shared/digest.md). It may overshoot a few lines into## Overview; that is acceptable and bounded. This is the entire brief-mode read of the page — step 4 additionally reads today's journal's mention(s) of this project, shrunk to fit. Those two are the whole of digest mode; nothing else is pre-loaded.Check before you use it: the read must contain a
Map:bullet. Task pages have no fixed template, so a property block can run long (extra task-specific properties push everything below it further down the file) — alimit 20read can land past the end of## Digestand return digest-shaped bullets with no Map. IfMap:is not in what you read, the property block is longer than the bound, not that the page lacks a Map — re-read with a largerlimit(e.g. 30), orgrep -nE '^(- )?## 'for the exact section span and read from there. Never present a digest whose Map you did not see — a digest without a Map is not a shorter digest, it is a page you cannot state coverage for.If that still shows no Map, check the span, not another guess at
limit. Bound a read to the exact## Digestsection — the heading line from the grep through the line before the next##heading. If that span-bounded read of the whole section still has noMap:bullet, the page genuinely lacks one: the property block was never the problem. Say so, treat this load's coverage as unknown until a rebuild, and offer to build a digest perskills/_shared/digest.md— the same offer step 2's no-## Digestfallback below makes.
What ships with it
2 files 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.
- 3d ago First seen · 134 lines · 96 tokens per session scan A 8d287f8ed490
brain-load is a skill published in the GitHub repository jame581/LogseqBrain (17 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 4,232 once invoked, about $0.0005 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 skills, from other repositories
curator-continuity
Use at the start of a build or coding session on a Curator-tracked project, and again when context runs low. Activates on "continue", "resume", "where did we leave off", "catch me up on this project", and on the save side "save state", "write a handoff", "checkpoint this", "I am running low on context", "before we…
my-curator
Use when interacting with the user's My Curator second brain via the my-curator MCP. Activates for READ ("what does my wiki say about X", "deep research my second brain", "find every source that mentions Y", "what does our cohort wiki say"), WRITE ("save to my wiki", "compile our findings", "put this in my projects…
review-implementing
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews. Activates on phrases like "implement this feedback", "address review comments", "fix review issues", "apply these suggestions", or when…
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification.
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
code-quality-check
Automated code quality verification checklist.