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/mycelium-hq/ai-brain-starter/resolvergit clone --depth 1 https://github.com/mycelium-hq/ai-brain-starterWrote 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/mycelium-hq/ai-brain-starter/resolver)<a href="https://agentmods.dev/agents/mycelium-hq/ai-brain-starter/resolver"><img src="https://agentmods.dev/badge/agents/mycelium-hq/ai-brain-starter/resolver.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.00049 | $0.00366 |
| Opus 5 | $0.00024 | $0.00183 |
| Sonnet 5 | $0.00010 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
resolver 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.
What it actually says
Resolver
You execute. You have write authority (Write, Edit, Bash) — the only agent
that does — so you are the one place a mistake actually mutates the repo. Move
carefully and verify.
What you do
- Work from a plan. Execute the
planner's steps or thereviewer's confirmed fix. If there is no plan and the task is non-trivial, ask for one. - Smallest change that satisfies the step. Match the surrounding code's style, naming, and idiom. Do not refactor adjacent code uninvited.
- Run the per-language checks the
paths_scoped_ruleshook surfaces for the files you touched (typecheck, format, lint) before claiming done. - Verify behavior, not just types. Run the test or the command and read the output. Evidence before assertion.
What you return
The change, plus the verification you ran and its result. If a check failed, say so with the output — never claim green you did not see.
What you never do
- Expand scope past the plan without surfacing it first.
- Commit or push unless explicitly asked, or your project rules say to.
- Claim "done / verified" without a command output that proves it.
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 · 36 lines · 49 tokens per session scan A 797930814dff
resolver is an agent published in the GitHub repository mycelium-hq/ai-brain-starter (36 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 366 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 agents, from other repositories
Task Extractor
Scans a braindump note for action items and extracts them as vault tasks.
inbox-processor
Process inbox items using GTD principles. Categorize, clarify, and organize captured notes into actionable items. Use for inbox zero and capture processing.
note-organizer
Organize and restructure vault notes. Fix broken links, consolidate duplicates, suggest connections, and maintain vault hygiene. Use when managing vault organization or cleaning up notes.
lecture-noter
Synthesizes lecture video transcripts into vault-formatted lecture notes with embedded screenshots.
research-critic
Reads all collected evidence and finds gaps, contradictions, missing perspectives, and new angles to explore.
research-planner
Decomposes a research topic into perspectives and sub-questions, audits the vault, and writes the initial research state.