clarify-question-loop

clarify-question-loop is a skill for Claude Code, Codex from agentlas-ai/Agentlas-OS. It costs 31 tokens per session (802 once invoked), scanned A, original, Apache-2.0.

A question flow for resolving the small number of ambiguities that could change an agent package, its permissions, its runtime setup, or whether it is private or public. It asks targeted questions instead of guessing.

In plain words
What is it for?
Use it before generating, packaging, publishing, or adapting an agent when important details are unclear, especially around roles, tools, permissions, synthesis, and release scope.
Why use it?
It prevents unsafe or unsuitable agent designs caused by missing requirements. It also helps decide whether one agent or several specialists should share the work and how their outputs depend on one another.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it before generating, packaging, publishing, or adapting an agent when important details are unclear, especially around roles, tools, permissions, synthesis, and release scope.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agentlas-ai/agentlas-os/clarify-question-loop
About the project

Agentlas OS is a local-first system for creating, storing, borrowing, and running specialist AI agents and temporary agent teams through supported hosts and models. It serves people who want reusable agents that remain available across computers and model workspaces, and the catalogue contains its skills, commands, hooks, agents, instructions, plugin, and rule.

agentlas-ai/Agentlas-OS · 1,613 stars · on GitHub · agentlas.cloud

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 agentlas-ai/Agentlas-OS --skill clarify-question-loop
Clone the repo
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS

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 clarify-question-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/clarify-question-loop/github.svg)](https://agentmods.dev/skills/agentlas-ai/agentlas-os/clarify-question-loop)
Your own site
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-os/clarify-question-loop"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/clarify-question-loop/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.

agentmods 80×15 button for clarify-question-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-os/clarify-question-loop"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/clarify-question-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 802 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 44
    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.00031 $0.00802
Opus 5.5 $0.00012 $0.00321
Sonnet 5.5 $0.00006 $0.00160
Haiku 4.5 $0.00003 $0.00080

Measured 1mo ago against content hash 6a4dc07b1445, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

clarify-question-loop 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 1mo 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.

.agents/skills/clarify-question-loop/SKILL.md · 75 lines

How it starts

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

Clarify Question Loop

Ask only questions that change the generated package, runtime adapter, safety boundary, or public/private release decision.

For /hep-build creation or behavior-changing packaging, this is not a substitute for the Builder Interview and Research Gate in contracts/builder-interview-research-gate.md. Run that gate first: ask an 8-12 question first batch, research similar agent repositories or comparables and academic/professional theory, then use this clarify loop only for the remaining narrow ambiguities.

Procedure

  1. Classify the current best mode.
  2. If single-agent vs team selection would change the package shape and the independent ownership boundaries are unclear, ask before generation. The first batch must include this plain-language question: "이 일을 한 명의 전문가가 처음부터 끝까지 맡으면 되나요, 아니면 조사/분석/검토처럼 여러 전문가가 나눠 맡고 마지막에 합쳐야 하나요?"
  3. Follow up on role count, role-specific tools/permissions, whether outputs must be synthesized, and whether artifacts are sequential dependencies or independent parallel packets.
  4. Identify missing facts that would change files or safety.
  5. Ask one to five short questions, preferably three. If more than five functional-quality questions remain, return to the Builder Interview and Research Gate instead of pretending the package is ready.
  6. Do not ask for secrets. Ask for secret names or setup boundaries instead.
  7. After answers arrive, re-run mode classification if needed.
  8. Generate or repair the package using the answers and list assumptions.

Budgets and stop rule (briefing interview engine)

This loop shares the briefing interview engine's contract (agentlas_cloud/interview/): a question is only worth asking if the answer would change execution, not just its phrasing. Respect the surface budget (chat 3-5 in one batch, stormbreaker <= 8 across two batches, build 8-12 plus follow-ups). 'decide later' is always a valid answer — record it as deferred, never re-ask. When answers you auto-confirmed from code/memory reach three in a row, the next question must go to the human.

Read the full file on GitHub · 75 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. 1mo ago First seen · 75 lines · 31 tokens per session scan A 6a4dc07b1445

Subscribe to this mod's changes

clarify-question-loop is a skill published in the GitHub repository agentlas-ai/Agentlas-OS (1,613 stars, last pushed 3d ago), licensed Apache-2.0. It adds 31 tokens to every session and 802 once invoked, about $0.0001 per session on Opus 5.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-30.

Related

Other skills, from other repositories

yait-aichain

Build AI features in Python — an LLM call, a multi-step pipeline, the same work over many items, or an agent that uses tools (web search, page fetching, your own functions, any REST API or MCP server, a working folder), asks a human before risky actions, stays within a money budget, or pauses and resumes — on any…

yaitio/aichain · 193 tokens

yait-aichain

Build AI features in Python — an LLM call, a multi-step pipeline, the same work over many items, or an agent that uses tools (web search, page fetching, your own functions, any REST API or MCP server, a working folder), asks a human before risky actions, stays within a money budget, or pauses and resumes — on any…

yaitio/aichain · 193 tokens

git-checkpoint

Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.

agentscope-ai/agentscope-java · 39 tokens

company-employee

The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…

Prism-Shadow/penguin-harness · 85 tokens

company-ceo

Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.

Prism-Shadow/penguin-harness · 56 tokens

pptagent

Create and revise editable PowerPoint presentations from a brief using HTML slide sources, rendering, and visual review. Use when the requested deliverable is a PPTX deck. The host authors the slides; text-only hosts can use an external visual reviewer.

icip-cas/PPTAgent · 52 tokens