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/frankchu91/mindbase-llm-wikiWrote 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/frankchu91/mindbase-llm-wiki/daily-brief)<a href="https://agentmods.dev/commands/frankchu91/mindbase-llm-wiki/daily-brief"><img src="https://agentmods.dev/badge/commands/frankchu91/mindbase-llm-wiki/daily-brief/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/frankchu91/mindbase-llm-wiki/daily-brief"><img src="https://agentmods.dev/badge/commands/frankchu91/mindbase-llm-wiki/daily-brief.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.00033 | $0.00319 |
| Opus 5 | $0.00016 | $0.00160 |
| Sonnet 5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
daily-brief 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 10d 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
Generate the daily brief for a project.
Arguments: $ARGUMENTS
Parse:
--project <id>or-p <id>flag → target project id.- First positional arg (if not a flag) → target project id (fallback).
- If neither present → uses
config.jsoncurrentProjectId. --date <iso>(default: today).
Call mindbase_generate_daily_brief({ projectId, date }). The tool reads all sources/contributors/<user>/<date>.md files for the chosen date and synthesizes a brief.
Write the brief to artifacts/briefs/<date>.md and return its path. Append a log entry (the MCP tool already does this).
Then present the brief inline to the user.
Note: -p / positional does NOT change current project — brief targets the specified project only.
Examples:
/mb:daily-brief→ current, today/mb:daily-brief -p ai-agents→ ai-agents, today/mb:daily-brief -p ai-agents --date 2026-07-05→ ai-agents, specific date/mb:daily-brief ai-agents --date 2026-07-05→ same (positional fallback)
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.
- 10d ago First seen · 28 lines · 33 tokens per session scan A 59af1eac9d3e
daily-brief is a command published in the GitHub repository frankchu91/mindbase-llm-wiki (99 stars, last pushed 16d ago), licensed MIT. It adds 33 tokens to every session and 319 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-30.
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-ingest
Process new source packets and synthesize them into wiki knowledge pages.
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.