MiMoCode is a terminal-based AI coding assistant that reads and writes code, runs commands, manages Git, and remembers project context across sessions. Developers use it to work with software projects through a command-line interface and connect it to language-model providers; the catalogue includes skills and instructions for it.
Borrowing it
Nothing to install: this file belongs to XiaomiMiMo/MiMo-Code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/XiaomiMiMo/MiMo-Code/main/.agents/skills/drive-mimo/SKILL.mdgit clone --depth 1 https://github.com/XiaomiMiMo/MiMo-CodeWrote 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/xiaomimimo/mimo-code/drive-mimo)<a href="https://agentmods.dev/skills/xiaomimimo/mimo-code/drive-mimo"><img src="https://agentmods.dev/badge/skills/xiaomimimo/mimo-code/drive-mimo/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/xiaomimimo/mimo-code/drive-mimo"><img src="https://agentmods.dev/badge/skills/xiaomimimo/mimo-code/drive-mimo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 414 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
- high Tool Misuse · line 457 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- medium Excessive Agency · line 114 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00091 | $0.04934 |
| Opus 5.5 | $0.00036 | $0.01974 |
| Sonnet 5.5 | $0.00018 | $0.00987 |
| Haiku 4.5 | $0.00009 | $0.00493 |
Grade D, and why
drive-mimo scanned grade D with 2 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 17d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
# Screen should still show prompt (not exit) Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$MHOME" "$WORKSPACE" How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drive MiMo
Overview
Two interfaces for driving a separate mimo process:
| Interface | Command | Use when |
|---|---|---|
| Headless | mimo run --format json |
Scripted tasks, CI, event validation |
| TUI | mimo in tmux |
Interactive flow, permission dialogs, keybindings, visual regression |
Core principle: Every run produces parseable evidence. No eyeballing.
Always drive an isolated instance: give each run a fresh MIMOCODE_HOME and a throwaway workspace so it never touches your own config, memory, or session DB.
Two ways to launch — orthogonal to interface
The interface (headless vs TUI, above) is what you drive. How the process is launched is a separate axis — either can be launched either way:
| Launcher | Command | Use when |
|---|---|---|
| Installed binary | mimo … |
Testing a released/installed build |
| Dev (from source) | bun dev … |
Debugging mimocode itself — runs src/index.ts directly, no build step, picks up local code changes |
Everything below uses mimo for brevity. To drive a dev build instead,
substitute bun dev for mimo and run from the repo root — every flag,
JSON event, and tmux technique is identical. See the Dev Mode section.
Prerequisites
# mimo binary must be on PATH (installed-binary launcher)
which mimo || echo "mimo not found on PATH"
# OR: dev launcher — run from the mimocode repo root, needs bun
which bun || echo "bun not found — needed for dev mode"
# tmux (for TUI interface)
which tmux || echo "tmux not found — install it for TUI mode"
Running the
wait-for-text.shhelper: invoke it as./scripts/wait-for-text.sh …from this skill's directory. The repository copy is executable and can be called directly.
Dev Mode (debugging mimocode itself)
When the goal is to debug mimocode's own code, launch from source with
bun dev instead of the installed mimo binary. It runs
packages/cli/src/index.ts directly — no build step — so local edits take
effect on the next launch.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 17d ago Changed · -1 lines 40738c240bc5
- 29d ago Changed a679673fc80b
- 2mo ago First seen · 458 lines · 91 tokens per session scan D 56df45543fa4
drive-mimo is a skill published in the GitHub repository XiaomiMiMo/MiMo-Code (13,737 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 4,934 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks the agent to reveal its instructions, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
dd-triage-flaky-test
Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
confirm-failures-are-causally-linked-to-the-task-before-reportin
When delegating a task affected by this skill, include.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.