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 sergezuber/FABULA-LLM-5 --skill askgit clone --depth 1 https://github.com/sergezuber/FABULA-LLM-5Wrote 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/sergezuber/fabula-llm-5/ask)<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>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.00054 | $0.00863 |
| Opus 5 | $0.00027 | $0.00432 |
| Sonnet 5 | $0.00011 | $0.00173 |
| Haiku 4.5 | $0.00005 | $0.00086 |
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.
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.
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 shortlabeland adescription). - 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 throughquestioninstead. - 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:
- Question tool absent (e.g.
run/eval, wherequestionis denied) — the tool isn't in your list. You never call it; decide and proceed directly. [Never-Ask]response (never-ask is on) — you do callquestion, 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.
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.
- 8d ago First seen · 59 lines · 54 tokens per session scan A 3bb9d1e20600
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.
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…
e2e-testing
ORGII keeps two separate E2E surfaces. Do not use one as proof for the other.
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…
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…
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…
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.