mimo-skill-creator

mimo-skill-creator is a skill for Claude Code, Codex from taxueseek/skill-optimizer. It costs 104 tokens per session (2,333 once invoked), scanned A, original, MIT.

A guide for creating, testing, optimizing, and packaging skills for MiMo Code, an AI coding assistant.

In plain words
What is it for?
Use it when building or maintaining MiMo Code skills, including their SKILL.md files, trigger descriptions, visibility settings, and supported directories.
Why use it?
It clarifies the settings MiMo Code reads and helps prevent skills from being placed or described in a way the assistant cannot discover correctly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/prove_skill.py <path-to-target-skill>.

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/taxueseek/skill-optimizer
agentmods
npx agentmods add skills/taxueseek/skill-optimizer/mimo-skill-creator

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mimo-skill-creator

README.md
[![agentmods](https://agentmods.dev/badge/skills/taxueseek/skill-optimizer/mimo-skill-creator.svg)](https://agentmods.dev/skills/taxueseek/skill-optimizer/mimo-skill-creator)
Your own site
<a href="https://agentmods.dev/skills/taxueseek/skill-optimizer/mimo-skill-creator"><img src="https://agentmods.dev/badge/skills/taxueseek/skill-optimizer/mimo-skill-creator.svg" alt="Measured on agentmods" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,333 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00104 $0.02333
Opus 5 $0.00052 $0.01167
Sonnet 5 $0.00021 $0.00467
Haiku 4.5 $0.00010 $0.00233

Measured 6d ago against content hash ae12ebf504e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

mimo-skill-creator 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.

mimo-skill-creator/SKILL.md · 266 lines

How it starts

The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill Creator — MiMo Code

Create skills that extend MiMo Code with specialized workflows. Leverages task, bash, read, write, edit, skill tools natively.

Three Gates (Pre-flight)

All must pass before starting. If any is no → stop.

  1. MiMo Code can't already do this well? → Skill is overhead.
  2. User will use it 5+ times? → One-shot → direct prompt.
  3. Model has it built-in? → Skill adds complexity, not value.

Skill Anatomy

skill-name/
├── SKILL.md          # Required — frontmatter + instructions
├── scripts/          # Optional — executable code
├── references/       # Optional — loaded on demand
└── assets/           # Optional — templates, icons, fonts

Frontmatter — only 3 fields are read by MiMo Code:

name: kebab-case       # Required. Letters, digits, hyphens. Max 64 chars.
description: >         # Required. Max 500 chars. Triggering conditions ONLY.
  Use when [trigger], [trigger], or [symptom].
hidden: true           # Optional. true = loaded but not in available_skills list.

Placement — MiMo Code discovers SKILL.md recursively from:

  • Project: .mimocode/skills/**, .claude/skills/**, .agents/skills/**, .codex/skills/**
  • Global: ~/.config/mimocode/skills/**, ~/.claude/skills/**, ~/.agents/skills/**
  • Config: skills.paths and skills.urls in mimocode.json

The #1 Mistake: Description Trap

When description summarizes the workflow, the model follows the description and skips the body.

# ❌ BAD: Summarizes workflow → model takes shortcut
description: Use for TDD — write test first, watch it fail, write minimal code

# ✅ GOOD: Triggering conditions only → forces model to read the body
description: Use when implementing features or bugfixes, before writing code

Formula: [Action verb] + [value]. Use when [trigger 1], [trigger 2], ... Include 5+ triggers. Add exclusions. Be slightly "pushy".

Creation: 7 Steps

1. Classify Complexity

Tier SKILL.md Dirs
Simple < 150 lines None
Medium 100-300 scripts/ or references/
Complex 200-650 Multiple

Read the full file on GitHub · 266 lines

Changes

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.

  1. 6d ago First seen · 266 lines · 104 tokens per session scan A ae12ebf504e1

Subscribe to this mod's changes

mimo-skill-creator is a skill published in the GitHub repository taxueseek/skill-optimizer (5 stars, last pushed 18d ago), licensed MIT. It adds 104 tokens to every session and 2,333 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens