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 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jame581/logseqbrain/brain-status"><img src="https://agentmods.dev/badge/skills/jame581/logseqbrain/brain-status.svg" alt="Reviewed on agentmods" width="80" 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.00089 | $0.00800 |
| Opus 5.5 | $0.00036 | $0.00320 |
| Sonnet 5.5 | $0.00018 | $0.00160 |
| Haiku 4.5 | $0.00009 | $0.00080 |
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 26d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain Status
Running the helper
- Bash:
sh "<this skill's base directory>/../_shared/bin/brain" <command> … - PowerShell-only Windows:
& "$(Split-Path (Split-Path (Get-Command git).Source))\bin\bash.exe" "<base>/../_shared/bin/brain" <command> … - Neither works: stop and say "logseq-brain needs Git for Windows (Git Bash) — https://git-scm.com/download/win".
- In Cowork, always pass
--graph <connected folder>. Elsewhere pass--graphonly when the graph is not configured. It may go anywhere on the line. On exit 2 withgraph not resolved, followskills/_shared/path-resolution.md, then pass--graph. - Put text arguments in single quotes; a
'inside becomes'\''. In double quotes the shell runs backticks and expands$. - Exit 0 clean, 1 findings (act on them), 2 error (act on its reason; don't retry blindly). Quote every
coverage:line. Never recompute a figure it printed. Itsgraph:line is the folder for your own Read, Edit and Write calls.
Run brain info once first. For "brain stats", follow references/analytics.md instead of the dashboard.
Dashboard
brain status: a TSV row per project and task page, then a counts line. The columns arepage type status last-updated digest-updated drift staleness focus next open. A page with no property block is listed asno properties — run brain-doctor.- Projects are the
Projects/rows whosetypeisproject. Leave other types out of the list and the counts. - Phrase
stalenessperskills/_shared/staleness.md. Whendriftis over 30, flag the row, and give the count once. - No digest (
digest-updatedis-), one page at a time:- "Currently:": the first bullet of
brain read <page> 'Current Plan' --max 8192. Over the cap, say "Current Plan is N KB — not read". - Latest activity:
brain tail <page> 'Session Log' --entries 1 --max 2048. - End with " projects have no digest — run brain-doctor to backfill".
- "Currently:": the first bullet of
- Cross-project decisions:
brain tail Decisions 'Decision Log' --entries 10 --max 4096. Keep those from the last 30 days. - Meta date:
Read pages/Meta.mdwithlimit 5, forlast-updated::. - Tasks: list active and blocked tasks by ID (with
focus). Collapse done tasks into "N done". List tasks with nostatusas "legacy — run brain-doctor to backfill". - Present, per project: name, status, staleness, drift, focus, open. Then tasks, decisions and totals. With no projects: "Your brain is empty. Use 'init brain project [name]' to add your first project."
brain activity 'viewed dashboard'.
What ships with it
1 file 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.
- 26d ago Changed · -25 lines 3fe76fe49b0b
- 1mo ago Changed · -38 lines 4174764e453b
- 1mo ago First seen · 101 lines · 89 tokens per session scan A d0bfaa141581
brain-status is a skill published in the GitHub repository jame581/LogseqBrain (18 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 800 once invoked, about $0.0004 per session on Opus 5.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
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
task-forest
Maintains a repo-local task forest or task DAG for the current workspace. Use when the user asks to initialize or update a task forest, close a session, summarize evolving project work, align a request with a global goal, track progress/history/deviations/todos, save or apply a task proposal, or export the…
conductor-new-track
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.