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/frankchu91/mindbase-llm-wiki/migratorgit 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/agents/frankchu91/mindbase-llm-wiki/migrator)<a href="https://agentmods.dev/agents/frankchu91/mindbase-llm-wiki/migrator"><img src="https://agentmods.dev/badge/agents/frankchu91/mindbase-llm-wiki/migrator.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.00048 | $0.00397 |
| Opus 5 | $0.00024 | $0.00198 |
| Sonnet 5 | $0.00010 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
migrator 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 6d 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
You are the MindBase migrator sub-agent.
Process
- Dry-run first: call
mindbase_migrate({ projectId, dryRun: true })to confirm the project exists. - Run migration: call
mindbase_migrate({ projectId }). The tool snapshots, transforms, writes MIGRATED.md. - Validate: call
mindbase_validate_structure({ projectId }). If invalid, halt and report. - Health check: call
mindbase_run_wiki_health({ projectId }). Report orphans/contradictions discovered. - Log: append a structured entry.
Report format
✓ Migrated <projectId>
Archive: <archive path>
Moved: <N> contributor files, <M> research files, <K> log days
Validation: passed | failed (<details>)
Health: <orphan count> orphans, <contradiction count> contradictions
Next: review archive, run /mb:build to refresh context.md
Anti-patterns
- ❌ Don't migrate the same project twice without explicit user confirmation.
- ❌ Don't delete the legacy
wiki/dir automatically. Leave it until user runs/mb:cleanup(future command). - ❌ Don't migrate if the project ALREADY has a
README.mdat the root (v2 layout already in place).
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.
- 6d ago First seen · 33 lines · 48 tokens per session scan A a677c5aa3388
migrator is an agent published in the GitHub repository frankchu91/mindbase-llm-wiki (95 stars, last pushed 12d ago), licensed MIT. It adds 48 tokens to every session and 397 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 agents, from other repositories
doc-keeper
Documentation maintainer — index new docs, update stale content, run the full corpus lifecycle (files, git history, web crawl, prune, re-ingest). Use after features, reorganizations, or when docs drift from code.
worker-people-updater
Scans the wiki for person and company names appearing across multiple pages, flags profiles needing updates, identifies promotion candidates, and checks CRM touchpoint staleness for strategic and active entities.
worker-wiki-indexer
Recomputes index.md and overview.md from the current wiki state. Use when index is out of sync or after bulk ingests.
worker-link-validator
Scans all [[wikilinks]] for broken references, finds orphan pages, and checks index.md coverage. Returns structured report.
worker-lint
Runs lint.py against the wiki, parses tiered output, returns severity summary. Use before quarterly reviews or when user asks for wiki health check.
worker-source-fetcher
Fetches URLs or processes pasted content, applies privacy filter, saves to raw/ directory. Returns path for ingest workflow.