handling-ambiguity

handling-ambiguity is a skill for Claude Code, Codex from New1Direction/korgex. It costs 20 tokens per session (280 once invoked), scanned A, original, MIT.

A decision-making method for unclear or incomplete requests. It separates facts that can be resolved from details that genuinely need a user choice.

In plain words
What is it for?
Use it to identify the few missing details that would change the implementation, resolve ordinary choices from context, and ask one focused question when necessary.
Why use it?
It avoids both needless questions and confident work based on assumptions that could lead to the wrong result.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the AskUserQuestion tool.

Good fit Use it to identify the few missing details that would change the implementation, resolve ordinary choices from context, and ask one focused question when necessary.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/new1direction/korgex/handling-ambiguity
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 New1Direction/korgex --skill handling-ambiguity
Clone the repo
git clone --depth 1 https://github.com/New1Direction/korgex

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 handling-ambiguity

README.md
[![agentmods](https://agentmods.dev/badge/skills/new1direction/korgex/handling-ambiguity/github.svg)](https://agentmods.dev/skills/new1direction/korgex/handling-ambiguity)
Your own site
<a href="https://agentmods.dev/skills/new1direction/korgex/handling-ambiguity"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/handling-ambiguity/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 handling-ambiguity

Your own site · 80×15
<a href="https://agentmods.dev/skills/new1direction/korgex/handling-ambiguity"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/handling-ambiguity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 280 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 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.00020 $0.00280
Opus 5 $0.00010 $0.00140
Sonnet 5 $0.00004 $0.00056
Haiku 4.5 $0.00002 $0.00028

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

Security

Grade A, and why

handling-ambiguity 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.

src/skills_builtin/handling-ambiguity/SKILL.md · 26 lines

What it actually says

Most failed tasks come from confidently building the wrong thing. Calibrate between asking and assuming — both extremes waste the user's time.

  1. Separate the unknowns. What can you resolve yourself from the code, the conventions, or sensible defaults? What genuinely changes what you'd build?
  2. Resolve what you can. For anything with an obvious or conventional answer, pick it, state the assumption, and proceed — don't ask about it.
  3. Ask only blocking, high-leverage questions. If an unknown would change the approach and you can't resolve it, ask ONE crisp question (offer concrete options). Use AskUserQuestion for real forks; don't ask permission to do the obvious.
  4. Scope check. If the request is huge or spans multiple subsystems, surface that and propose a decomposition before diving in.
  5. When you proceed on assumptions, make them visible so the user can correct course early rather than after the work is done.

Red flags: asking a question you could answer by reading one file; OR building for 20 minutes on an unstated assumption that turns out wrong.

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 · 26 lines · 20 tokens per session scan A d49a2edbc42b

Subscribe to this mod's changes

handling-ambiguity is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 280 once invoked, about $0.0001 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.