compose:ask

compose:ask is a skill for Claude Code, Codex from XiaomiMiMo/MiMo-Code. It costs 54 tokens per session (859 once invoked), scanned A, original, MIT.

A guide for asking users for decisions, clarification, or approval through structured questions.

In plain words
What is it for?
Use it when a task needs user input, such as selecting an option, clarifying requirements, or approving a proposed change.
Why use it?
It prevents work from stopping with vague questions and keeps important choices explicit and easy to answer.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when a task needs user input, such as selecting an option, clarifying requirements, or approving a proposed change.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xiaomimimo/mimo-code/ask
About the project

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.

XiaomiMiMo/MiMo-Code · 12,961 stars · on GitHub · mimo.xiaomi.com

Install

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.

Any agent
npx skills add XiaomiMiMo/MiMo-Code --skill ask
Clone the repo
git clone --depth 1 https://github.com/XiaomiMiMo/MiMo-Code

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 compose:ask

README.md
[![agentmods](https://agentmods.dev/badge/skills/xiaomimimo/mimo-code/ask.svg)](https://agentmods.dev/skills/xiaomimimo/mimo-code/ask)
Your own site
<a href="https://agentmods.dev/skills/xiaomimimo/mimo-code/ask"><img src="https://agentmods.dev/badge/skills/xiaomimimo/mimo-code/ask.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 859 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

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 →

  • medium Excessive Agency · line 49
    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.
How audits are shown
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.00054 $0.00859
Opus 5 $0.00027 $0.00430
Sonnet 5 $0.00011 $0.00172
Haiku 4.5 $0.00005 $0.00086

Measured 5d ago against content hash 618bf99c5e19, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

compose:ask 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

packages/opencode/src/skill/compose/.bundle/ask/SKILL.md · 58 lines

How it starts

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

Asking the User

The Rule

Every time you need the user to decide, clarify, or approve something, route it through the question tool. Never stop the loop with a natural-language question ("Does this look right?", "Should I proceed?", "Which would you prefer?"). A natural-language question ends your turn without finishing the task; a question tool call does not.

This means: the loop only ends when the task is actually complete — never because you paused to ask in prose.

How to Ask

  • Structured options — when the decision has known choices, list them as options (each with a short label and a description).
  • Open-ended — when you can't enumerate good options, pass empty options. An empty options list renders as a free-text prompt: the user types whatever they want. So anything you'd normally ask in prose can be asked through question instead.
  • One question per concern — don't bundle unrelated decisions; ask them as separate questions (or separate calls).
  • Don't repeat the question in prose — the tool already renders it. Just call the tool.
question({
  questions: [{
    question: "Which auth strategy should I use?",
    header: "Auth",
    options: [
      { label: "Session cookies", description: "Server-side sessions, simplest" },
      { label: "JWT", description: "Stateless, good for multiple services" },
    ],
  }],
})

When No User Is Available

There are two situations where you won't get a human answer. The decision behavior is identical in both — you pick the best option for unattended/headless execution yourself and keep going. They differ only in whether the question tool is reached this turn:

  1. Question tool absent (e.g. run/eval, where question is denied) — the tool isn't in your list. You never call it; decide and proceed directly.
  2. [Never-Ask] response (never-ask is on) — you do call question, but instead of a user answer the tool returns a [Never-Ask] directive. Re-pick from the options you proposed, explicitly state your choice and reasoning in your response text, and continue.

Read the full file on GitHub · 58 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. 5d ago First seen · 58 lines · 54 tokens per session scan A 618bf99c5e19

Subscribe to this mod's changes

compose:ask is a skill published in the GitHub repository XiaomiMiMo/MiMo-Code (12,961 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 859 once invoked, about $0.0003 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-09-03.