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.
git clone --depth 1 https://github.com/eliransu/digital-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/commands/eliransu/digital-brain/sup)<a href="https://agentmods.dev/commands/eliransu/digital-brain/sup"><img src="https://agentmods.dev/badge/commands/eliransu/digital-brain/sup/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/commands/eliransu/digital-brain/sup"><img src="https://agentmods.dev/badge/commands/eliransu/digital-brain/sup.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.00029 | $0.00130 |
| Opus 5.5 | $0.00012 | $0.00052 |
| Sonnet 5.5 | $0.00006 | $0.00026 |
| Haiku 4.5 | $0.00003 | $0.00013 |
Grade A, and why
sup 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 1mo 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.
What it actually says
Invoke the sup skill from the digital-brain plugin. Follow its SKILL.md exactly: live-query Gmail, Slack, Linear, and Google Calendar to produce a compact dashboard of what's blocking me, today's meetings, recent mentions (48h), my open Linear issues grouped by status, and "who does what" for issues I opened that others own. End with a single concrete next-move suggestion. Do NOT write to the vault — this is read-only.
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.
- 1mo ago First seen · 6 lines · 29 tokens per session scan A 1de980d237e3
sup is a command published in the GitHub repository eliransu/digital-brain (1 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 130 once invoked, about $0.0001 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-31.
Other commands, from other repositories
status
Dashboard for a project — line counts, last build, contributors, file totals. Usage: /mb:status [-p ] [project-id].
daily-brief
Generate today's brief from sources/contributors/. Usage: /mb:daily-brief [-p ] [project-id] [--date YYYY-MM-DD].
migrate
Convert a legacy MindBase project (wiki/-based) to the v2 layout. Usage: /mb:migrate [--project ] [--all] [--dry-run].
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
weekly-update
Run the weekly hub pass in one session: mine new lessons (transcripts, an optional course source, social sources) and discoveries, consolidate the lessons, triage both changelogs, check pinned third-party skills against their upstream, audit every tracked project area against one shared trace, rank top tips, then put…