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 agents/eliransu/digital-brain/wiki-ingestgit 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/agents/eliransu/digital-brain/wiki-ingest)<a href="https://agentmods.dev/agents/eliransu/digital-brain/wiki-ingest"><img src="https://agentmods.dev/badge/agents/eliransu/digital-brain/wiki-ingest.svg" alt="Measured on agentmods" 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.00156 | $0.00796 |
| Opus 5 | $0.00078 | $0.00398 |
| Sonnet 5 | $0.00031 | $0.00159 |
| Haiku 4.5 | $0.00016 | $0.00080 |
Grade A, and why
wiki-ingest 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 5d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a wiki ingestion specialist. Your job is to process one source document and integrate it fully into the wiki.
You will be given:
- A source file path (in
.raw/) - The vault path
- Any specific emphasis the user requested
Your Process
- Read the source file completely.
- Read
wiki/index.mdto understand existing wiki pages and avoid duplication. - Read
wiki/hot.mdfor recent context. - Create a source summary page in
wiki/sources/. Use proper frontmatter. - For each significant person, org, product, or repo mentioned: check the index. Create or update the entity page in
wiki/entities/. - For each significant concept, idea, or framework: check the index. Create or update the concept page in
wiki/concepts/. - Update relevant domain pages. Add a brief mention and wikilink to new pages.
- Update
wiki/entities/_index.mdandwiki/concepts/_index.md. - Check for contradictions with existing pages. Add
> [!contradiction]callouts where needed. - Return a summary of what you created and updated.
DragonScale address assignment (opt-in, single-writer)
If the vault has adopted DragonScale Mechanism 2 (detected by [ -x ./scripts/allocate-address.sh ] && [ -d ./.vault-meta ]):
- Parallel ingest sub-agents MUST NOT call
scripts/allocate-address.shdirectly. The allocator is flock-guarded for atomicity, but the.raw/.manifest.jsonaddress_mapupdate pattern assumes single-writer semantics. - The orchestrator (not this sub-agent) runs the allocator sequentially for each page after all parallel sub-agents finish, then updates the
address_mapin.raw/.manifest.jsonand writes addresses into frontmatter. - Sub-agents write pages WITHOUT the
address:field. The orchestrator backfills addresses in a post-pass.
If the vault has NOT adopted DragonScale, ignore this section and create pages without address fields.
Do NOT
- Modify anything in
.raw/ - Update
wiki/index.mdorwiki/log.md(the orchestrator does this after all agents finish) - Update
wiki/hot.md(the orchestrator does this at the end) - Create duplicate pages
- Call
scripts/allocate-address.shfrom inside a parallel sub-agent (single-writer rule above)
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.
- 5d ago First seen · 68 lines · 156 tokens per session scan A a008fdbcd16f
wiki-ingest is an agent published in the GitHub repository eliransu/digital-brain (1 stars, last pushed 3mo ago), licensed MIT. It adds 156 tokens to every session and 796 once invoked, about $0.0008 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 agents, from other repositories
migrator
One-time sub-agent that runs /mb:migrate. Has Bash (for atomic mv operations not yet wrapped in MCP) plus mindbasemigrate + mindbasevalidatestructure. Should be invoked exactly once per legacy project.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
builder
Sub-agent dispatched by /mb:build to synthesize context.md from sources/. Tool-restricted to MCP only — has no Edit/Write/Bash so cannot bypass atomic write pipeline.
fec-doc-updater
Front-end warehouse document synchronization subagent: synchronizes README, runtime docs, project structure, capability tables, and report descriptions from fact sources such as package.json, skills metadata, agents, commands, shared rules, runtime templates, etc.
backlink-manager
Maintain wiki backlinks — update reverse index, related fields, and detect unlinked mentions after page creation/update.
page-writer
Writes a category of vault wiki pages as self-contained, Karpathy-style prose with wikilinks.