compose:ask

compose:ask is a skill for Claude Code, Codex from sergezuber/FABULA-LLM-5. It costs 54 tokens per session (863 once invoked), scanned A, a copy of compose:ask, MIT.

A workflow rule for handling decisions, clarifications, and approvals during a coding task. It requires these requests to go through a structured question tool, including when the user is unavailable.

In plain words
What is it for?
It helps an agent ask for choices, approvals, or missing information, and decide how to proceed when no user or question tool is available.
Why use it?
It prevents work from stopping with an unanswered question in ordinary chat and keeps decisions clear and actionable.

Skill for Claude CodeCodex

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

Good fit It helps an agent ask for choices, approvals, or missing information, and decide how to proceed when no user or question tool is available.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sergezuber/fabula-llm-5/ask
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 sergezuber/FABULA-LLM-5 --skill ask
Clone the repo
git clone --depth 1 https://github.com/sergezuber/FABULA-LLM-5

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/sergezuber/fabula-llm-5/ask.svg)](https://agentmods.dev/skills/sergezuber/fabula-llm-5/ask)
Your own site
<a href="https://agentmods.dev/skills/sergezuber/fabula-llm-5/ask"><img src="https://agentmods.dev/badge/skills/sergezuber/fabula-llm-5/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 863 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.
Origin 95% copy Near-identical to another mod 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.00863
Opus 5 $0.00027 $0.00432
Sonnet 5 $0.00011 $0.00173
Haiku 4.5 $0.00005 $0.00086

Measured 8d ago against content hash 3bb9d1e20600, 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 8d 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

This is a copy

95% identical to compose:ask — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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

How it starts

The opening of the file, as written. The whole thing — 59 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 · 59 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. 8d ago First seen · 59 lines · 54 tokens per session scan A 3bb9d1e20600

Subscribe to this mod's changes

compose:ask is a skill published in the GitHub repository sergezuber/FABULA-LLM-5 (83 stars, last pushed 6d ago), licensed MIT. It adds 54 tokens to every session and 863 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to compose:ask, differing in 1 line, and is treated as a copy.

Related

Other skills, from other repositories

architecture-audit

Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…

org2AI/ORG2 · 70 tokens

e2e-testing

ORGII keeps two separate E2E surfaces. Do not use one as proof for the other.

org2AI/ORG2 · 0 tokens

dual-instance-verification

Dual-instance (双机) real-machine verification protocol for ORG2 cloud sync and session sharing. Use before declaring any sharing/sync/collab feature or fix "verified": share/unshare, push/retract, fork/import, comments, member-floor, replay, continuation, or anything touching Org2CloudSyncEngine, collab engines, or the…

org2AI/ORG2 · 0 tokens

org2-performance-guard

Prevent CPU, RAM, I/O, background-work, and false-green lifecycle regressions in ORG2. Use when adding or reviewing polling, timers, Realtime subscriptions, event listeners, workers, streaming paths, caches, pagination, provider-owned transcript ingestion or identity/dedupe, external-history scans, cloud sync…

org2AI/ORG2 · 112 tokens

react-best-practices

ORGII-specific React 19 performance review and implementation guidance, adapted from Vercel Engineering. Use for React performance, re-render, async waterfall, bundle, heavy dependency, virtualization, high-frequency event, Context/provider, or store-subscription work. Do not trigger for styling, copy changes, or…

org2AI/ORG2 · 77 tokens

create-orgii-agent

Create or modify a custom ORGII agent definition (and the org it belongs to). Use when the user wants to create, configure, retune, rename, or delete an agent, define an agent's soul / capabilities / tools, organise agents into an org, or asks about agent-definitions.json.

org2AI/ORG2 · 67 tokens