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 SanderMoon/local-brain --skill brain-dailygit clone --depth 1 https://github.com/SanderMoon/local-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/skills/sandermoon/local-brain/brain-daily)<a href="https://agentmods.dev/skills/sandermoon/local-brain/brain-daily"><img src="https://agentmods.dev/badge/skills/sandermoon/local-brain/brain-daily/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/sandermoon/local-brain/brain-daily"><img src="https://agentmods.dev/badge/skills/sandermoon/local-brain/brain-daily.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.00043 | $0.01072 |
| Opus 5.5 | $0.00017 | $0.00429 |
| Sonnet 5.5 | $0.00009 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
brain-daily 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brain-daily: Daily Planning Workflow
Start the day with a structured overview of the user's Local Brain workspace. This is the "engage" phase — the daily habit that keeps work intentional.
Trigger Phrases
- "Good morning", "start my day", "morning briefing"
- "What should I focus on today?"
- "What's on my plate?" / "Catch me up" / "What's due?"
Pre-flight Check
Call get_brain_overview first. If the brain is empty (no projects, no dump items), do not run a briefing on nothing. Instead suggest:
"Your brain is empty — let's set it up first. Tell me about what you're working on."
This naturally transitions to the brain-setup workflow.
Workflow
Step 1 — Fetch the Briefing
Call get_daily_briefing to retrieve:
- Overdue tasks (most urgent)
- Tasks due today
- High-priority open tasks
- In-progress work
- Blocked items
- Recent completions
- Inbox items awaiting refile
Step 2 — Summarize Clearly
Present a concise, scannable summary. Do not dump raw data.
Project Overview Table
Always start with a project overview table showing the distribution of tasks. Use the project_summaries data:
| Project | Open | Backlog | Total |
|--------------------|------|---------|-------|
| agentic-project | 15 | 6 | 21 |
| nsa2d | 8 | 3 | 11 |
| ... | ... | ... | ... |
Open = actionable tasks (status: open, in-progress, blocked). Backlog = parked for later (status: backlog). This distinction is critical — backlog items are not on the user's plate today.
Actionable Items
After the table, list actionable items grouped by urgency. Only show items with status open, in-progress, or blocked — never backlog:
- Overdue — flag prominently with task IDs and due dates
- Due today — list with IDs
- In progress — what is already underway
- High priority (open) — P1 tasks that are open (not backlog), without due dates
- Blocked — items needing unblock
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 · 113 lines · 43 tokens per session scan A 1fe089e0f3ab
brain-daily is a skill published in the GitHub repository SanderMoon/local-brain (9 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 1,072 once invoked, about $0.0002 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 skills, from other repositories
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
community
Use when building or running a persistent two-way community space — Discord, Telegram, Circle: platform choice, structure, onboarding, native→bot→human moderation, rituals, growth loops, health metrics. NOT churn of paying product customers (that is retention), NOT broadcast email (that is newsletter), NOT one live…
parallel
Use when two or more pieces of work are genuinely independent — disjoint files, no shared state, no ordering edge — and should fan out across subagents, then be gathered and reconciled under a combined test suite. Decides WHAT can run concurrently; NOT the isolation it runs in (that is worktrees), NOT the per-unit TDD…
codebase-navigation
Use this skill when starting work in an unfamiliar codebase or area — finding where something is implemented, how a request flows, what depends on a piece of code, or where a change should go — before reading files one by one. Triggers: user says "where is", "how does this work", "find the code that", "explain this…
slackcli
Read, send, search, and manage Slack workspaces with the slackcli binary. Installs slackcli if missing and checks or proposes authentication first. Use whenever the user mentions Slack or pastes a slack.com link.
tokf-discover
Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.