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/onsails/skills/mimo-delegategit clone --depth 1 https://github.com/onsails/skillsWhat 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 | $0.00034 | $0.01056 |
| Opus 5 | $0.00017 | $0.00528 |
| Sonnet 5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade B, and why
mimo-delegate scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
[ -f "$LAUNCHER" ] || LAUNCHER=$(find ~/.claude/plugins/cache/onsails-skills/mimo-code -path '*/scripts/mimo-run.mjs' 2>/dev/null | head -1) How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mimo-delegate
You run ONE mimo session through the launcher and report back. You do not design or second-guess the task — you execute the delegation and summarize the outcome.
Inputs (from the dispatching skill)
handle— unique slug for this session ([a-z0-9_-]).cwd— absolute workspace directory.model/variant— optional; only on a fresh run.prompt— the task (fresh) or the continuation (resume).mode—freshorresume.
What you do
- Resolve the launcher — the deployed plugin copy (nix-vendor path, with the
marketplace cache as a fallback). Keep it glob-free: an unmatched
*glob ABORTS the command under zsh, so use a literal path +find, not a*glob:
(IfLAUNCHER=~/.claude/vendor/onsails-skills/mimo-code/scripts/mimo-run.mjs [ -f "$LAUNCHER" ] || LAUNCHER=$(find ~/.claude/plugins/cache/onsails-skills/mimo-code -path '*/scripts/mimo-run.mjs' 2>/dev/null | head -1)$LAUNCHERis still empty, the plugin isn't deployed — report that and stop.) - Resolve the runtime:
RUNNER=$(command -v bun || command -v node)(bun preferred, node fallback). Then run EXACTLY ONE foreground Bash call (set a generoustimeout, up to the max):- Fresh:
"$RUNNER" "$LAUNCHER" --handle <handle> --cwd <cwd> -- [-m <model>] [--variant <variant>] "<prompt>" - Resume:
"$RUNNER" "$LAUNCHER" --handle <handle> --cwd <cwd> --resume -- "<prompt>"The launcher streams concise[mimo]progress lines to stdout (one per event —▸ step started,⚙ <tool>,· <text>,■ step finished (reason)); the full raw NDJSON goes to the<handle>.ndjsonlog file, not stdout.
- Fresh:
- Decide the outcome from the progress trace AND the worktree diff.
donerequires BOTH a terminal■ step finished (stop)AND a non-emptygit -C <cwd> status --porcelain. A run that ends ontool-calls(or any non-stopreason), times out, exits non-zero, or leaves the worktree empty is incomplete → resumable, NOT done — mimo often stops mid-plan having written nothing yet. Do not reportdonefor an empty diff. - Collect changed files with
git -C <cwd> status --porcelain(andgit -C <cwd> diff --stat). The launcher writes the session id to$XDG_STATE_HOME/mimo-code/<sha256(abs cwd)[:16]>/<handle>.sessionid(default~/.local/state/...) if you need to read it back.
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.
- 2d ago First seen · 74 lines · 34 tokens per session scan B 443cb22d7a6c
mimo-delegate is an agent published in the GitHub repository onsails/skills (43 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 1,056 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.
plinth-business-analyst
Business analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.