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 commands/eliransu/digital-brain/syncgit clone --depth 1 https://github.com/eliransu/digital-brainWhat 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.00041 | $0.00153 |
| Opus 5 | $0.00020 | $0.00077 |
| Sonnet 5 | $0.00008 | $0.00031 |
| Haiku 4.5 | $0.00004 | $0.00015 |
Grade A, and why
sync 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.
What it actually says
Invoke the sync skill from the digital-brain plugin. Follow its SKILL.md exactly: pull from Gmail, Slack, Linear, and Google Calendar for the last 48h (24h for Slack DMs), file results into wiki/daily/<today>/{mentions.md, topics.md, linear.md, calendar.md}, dedupe by stable ID if the date folder already exists, append new items under ## Update HH:MM, and print all collected items as bullets grouped by source at the end.
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 · 6 lines · 41 tokens per session scan A c952c3d754bc
sync is a command published in the GitHub repository eliransu/digital-brain (1 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 153 once invoked, about $0.0002 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-31.
Other commands, from other repositories
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-req
Capture and decompose a concept into atomic, traceable wiki requirements. Clarifies ambiguous requirements, splits them into atomic pieces, and persists them as wiki/requirements/ pages with status tracking.
wiki-record
Capture the just-completed task's tool-call trajectory into the wiki as agent working-memory, then optionally distill it into a reusable skill.
wiki-retro
Save an atomic insight from the current task into the wiki. Creates a single markdown file that layered recall surfaces in future sessions.
wiki-discover
Auto-discover new sources from the web. Searches based on config topics and known knowledge gaps.
wiki-init
Initialize a new LLM Wiki in the current directory. Creates the full directory structure, config, and template files.