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-savenpx skills add jame581/LogseqBrain --skill brain-savegit 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.00077 | $0.02849 |
| Opus 5 | $0.00039 | $0.01425 |
| Sonnet 5 | $0.00015 | $0.00570 |
| Haiku 4.5 | $0.00008 | $0.00285 |
Grade A, and why
brain-save 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 2d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain Save
Persist session context — decisions, progress, plans, implementation details — to the Claude Brain Logseq graph for cross-session and cross-device continuity.
Prerequisites
Resolve the graph path per skills/_shared/path-resolution.md.
What to Save
Six categories — see references/categories.md for each one's format and rules. The orchestrator decides which apply based on what the session covered:
- Session Log Entry (always)
- Decisions (when made — see
references/decisions.mdfor conflict + cross-project rules) - Plan Updates (when plans changed — replace, don't append)
- Implementation Details (when significant)
- Jira Task Context (when tasks were worked on — store pointers, not full plans)
- User Preferences & Meta (when newly discovered — update
pages/Meta.md)
Save Process
-
Identify target project(s). Look for project names mentioned, files/repos discussed, or explicit user statements ("we're working on X"). If multiple projects, save to each. If unclear, ask: "This touched [X] and [Y] — save to both?"
-
Verify project page exists. Glob for
pages/Projects___<ProjectName>.md. If missing:- Tell user: "No project page found for [name]. Want me to create one first?"
- If yes, hand off to
brain-init"Adding a New Project" flow, then continue. - If no, list available projects and let the user pick.
- Never write session data to a non-existent project page.
Task pages: a save may also target a task page (
pages/Tasks___<ID>.md) when the session was about that task. Task pages have no fixed template, but their page-top property block must containstatus::with one ofactive | blocked | done. If the page exists withoutstatus::, seedstatus:: activeas part of this save. If the session content signals completion ("merged", "deployed", "closed", "released", "hotovo"), suggeststatus:: done— never write a status change the user didn't confirm (same rule as auto-save). If no task page exists for a worked task, keep the Current Plan pointer entry only — don't createTasks___<ID>.mduninvited; offer to create one and only do so if the user wants it.
What ships with it
4 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.
- 2d ago First seen · 96 lines · 77 tokens per session scan A af1e2bdbfc96
brain-save is a skill published in the GitHub repository jame581/LogseqBrain (17 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 2,849 once invoked, about $0.0004 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.