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-statusnpx skills add jame581/LogseqBrain --skill brain-statusgit clone --depth 1 https://github.com/jame581/LogseqBrainWrote 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/jame581/logseqbrain/brain-status)<a href="https://agentmods.dev/skills/jame581/logseqbrain/brain-status"><img src="https://agentmods.dev/badge/skills/jame581/logseqbrain/brain-status.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 | $0.00089 | $0.02177 |
| Opus 5 | $0.00044 | $0.01089 |
| Sonnet 5 | $0.00018 | $0.00435 |
| Haiku 4.5 | $0.00009 | $0.00218 |
Grade A, and why
brain-status 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain Status
Display a quick dashboard of all projects in the Claude Brain graph — status, last activity, current focus, blockers.
Modes
- Dashboard (default, "brain status" / "show projects" / …): the per-project overview in "Dashboard Generation" below.
- Analytics ("brain stats" / "graph analytics" / "graph activity over time"): the aggregate counts in "Analytics (brain stats)" below.
Both resolve the graph path first (Prerequisites). Pick the mode from the trigger phrase; if ambiguous, default to Dashboard.
Prerequisites
Resolve the graph path per skills/_shared/path-resolution.md.
Dashboard Generation
-
Census first — this decides what appears. Glob (or
ls)pages/Projects___*.mdandpages/Tasks___*.md— one free call. This file list, not the ripgrep in step 2, is authoritative for "what's in my brain": a page belongs on the dashboard because it exists, not because a later grep happened to match its content. At census time you have filenames only, so apply only the exclusion a filename can decide: drop pages ending___SessionArchive.md. Do not try to filter ontype::here — that requires reading each file, which would turn one free call into 45, and step 2's ripgrep already returnstype::for every page. The census is therefore a candidate list; step 2 narrows it. -
Collect every census page's state in one call. Digest properties make the whole dashboard greppable:
rg "^(type|status|last-updated|focus|next|open|digest-updated):: " pages/ \ -g "Projects___*.md" -g "Tasks___*.md"One result set gives, per page with a readable property block: its type, status, freshness, current focus, next action, and any open blocker. This is where
type::becomes available, so this is where the type-based exclusions happen — the census (step 1) could not make them. Drop from the candidate list: any page withtype:: session-archive, and anyProjects___*.mdwhosetype::is notproject— e.g.type:: task-index(a project's task inventory, likeProjects___Unicorn-Globus___Tasks.md) ortype:: project-note(a standalone note, likeProjects___Unicorn-Globus___ClaudeCodeAutomation.md). Both match the glob but are not projects; counting them would inflate the dashboard and the "N projects have no digest" line with pages that were never supposed to carry one (skills/_shared/digest.md's scope rule). A census page with notype::at all is not excluded here — it has a damaged or missing property block, and step 3 surfaces it rather than dropping it.
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 · 101 lines · 89 tokens per session scan A d0bfaa141581
brain-status is a skill published in the GitHub repository jame581/LogseqBrain (17 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 2,177 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.