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 skills add onsails/skills --skill mimo-codegit clone --depth 1 https://github.com/onsails/skillsWrote 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/skills/onsails/skills/mimo-code)<a href="https://agentmods.dev/skills/onsails/skills/mimo-code"><img src="https://agentmods.dev/badge/skills/onsails/skills/mimo-code/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/skills/onsails/skills/mimo-code"><img src="https://agentmods.dev/badge/skills/onsails/skills/mimo-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.01338 |
| Opus 5.5 | $0.00030 | $0.00535 |
| Sonnet 5.5 | $0.00015 | $0.00268 |
| Haiku 4.5 | $0.00007 | $0.00134 |
Grade A, and why
mimo-code 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 1mo 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mimo-code
Overview
Delegate a write-capable coding session to mimo, staying the conductor. Heavy
work and tokens move to mimo; you orchestrate and review the diff.
When to use
- The user invokes
/mimo-code [provider/model] [variant] <task>or asks to run/resume mimo. - A prior mimo session needs continuation (it asked something or was cut off).
The rule that shapes everything
Never run mimo in the main thread. ALWAYS dispatch the mimo-delegate subagent
(model sonnet) so the live NDJSON stream and any blocking stay out of the main
context. You only ever receive its distilled summary.
Parse the invocation
Raw slash-command arguments: $ARGUMENTS
Interpret as [provider/model] [variant] <task> (empty when triggered by description match rather than /mimo-code — then read intent from the user's message):
- A leading
xxx/yyytoken → model. A followingminimal|low|medium|high|max→ variant. - The rest is the task;
resume/continue→ resume the recorded session (see Resume). Natural-language requests map the same way.
Resolve the model — ASK, do not default (only when no model was given, fresh runs only)
- Gather options via the
mimo-resolvesubagent (model sonnet). It runs theresolve-modelslauncher and returns the authenticated provider∩modeloptionsandvariants— keeping the catalogue output out of the conductor's context. Empty options (no authenticated provider) → STOP and tell the user to runmimo providers login. - Using the returned
options(the authenticated intersection — count models, not providers): Exactly one usable model → auto-pick (asking is pointless). ≤4 → one AskUserQuestion listing them. >4 (the common real case — a single provider can expose dozens) → narrow, never dump: AskUserQuestion the provider first (the authenticated set is small), then AskUserQuestion ≤4 models for that provider — lead withmimo-resolve's recommended id, and rely on the auto-added Other free-text for the long tail. One authenticated provider offering several models is still "more than one" → ASK; "low-risk"/"mechanical"/cost or proactivity never justify a silent pick, and printing the whole catalogue for the user to retype an id verbatim is the anti-pattern to avoid. - Ask effort/variant with a ≤4 menu — AskUserQuestion caps at 4 options, so
you cannot list all five variants + a default. Offer
default(omit--variant) plus a few variants, each with a one-line description (defaultis the safe recommendation for a one-shot delegation);minimal/mediumreach via Other.
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.
- 1mo ago First seen · 86 lines · 75 tokens per session scan A 50d30f45a5e4
mimo-code is a skill published in the GitHub repository onsails/skills (44 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,338 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
add-cloud-flow
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.