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 Inference1/clarify-intent-and-establish-shared-understanding --skill clarify-intent-and-establish-shared-understandinggit clone --depth 1 https://github.com/Inference1/clarify-intent-and-establish-shared-understandingWrote 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/inference1/clarify-intent-and-establish-shared-understanding/clarify-intent-and-establish-shared-understanding)<a href="https://agentmods.dev/skills/inference1/clarify-intent-and-establish-shared-understanding/clarify-intent-and-establish-shared-understanding"><img src="https://agentmods.dev/badge/skills/inference1/clarify-intent-and-establish-shared-understanding/clarify-intent-and-establish-shared-understanding/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.
<a href="https://agentmods.dev/skills/inference1/clarify-intent-and-establish-shared-understanding/clarify-intent-and-establish-shared-understanding"><img src="https://agentmods.dev/badge/skills/inference1/clarify-intent-and-establish-shared-understanding/clarify-intent-and-establish-shared-understanding.svg" alt="Reviewed on agentmods" width="80" 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.00286 | $0.00933 |
| Opus 5 | $0.00143 | $0.00466 |
| Sonnet 5 | $0.00057 | $0.00187 |
| Haiku 4.5 | $0.00029 | $0.00093 |
Grade A, and why
clarify-intent-and-establish-shared-understanding 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 11d 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.
What it actually says
Interrogate the user systematically until both sides share a precise, complete understanding of the intent, problem, goal, task, constraints, priorities, assumptions, and desired outcome.
Construct and navigate an implicit decision tree. Resolve foundational choices before dependent ones, identify hidden assumptions, detect contradictions, and revisit previous conclusions when new information changes the decision landscape.
Proceed through the decision tree iteratively, one round at a time. At each round, define the frontier as the set of decisions whose prerequisites have already been resolved; in other words, it consists of the questions that can be asked without making assumptions about information that has not yet been provided. Present all questions on the current frontier within a single round, number them sequentially, and provide a recommended answer for each question. Do not proceed to the next round until the user has responded to the questions presented in the current round.
Format a round like so:
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
---
❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
In each round, the user's answers reshape the decision tree: resolved decisions extend the frontier and unlock questions that depend on them. Recompute the frontier accordingly and then present the next round of questions. Any question whose answer depends on another unresolved question in the current round should be deferred to a subsequent round.
Do not combine independent questions. Each question should:
- target a specific unresolved decision or ambiguity;
- briefly explain why the answer affects the outcome;
- provide a clearly labeled recommended option when sufficient context exists;
- preserve user agency by making clear that the final choice belongs to the user.
Do not ask for information that can be reliably obtained from available context, code repositories, files, tools, connected sources, or other authorized inputs. Retrieve or verify such information directly when possible. Reserve questions for human judgment, preferences, priorities, acceptable risks, subjective trade-offs, or unavailable facts.
Continuously restate and refine the emerging understanding. Identify ambiguities, contradictions, unresolved dependencies, missing success criteria, and differences between stated requests and likely underlying goals.
Continuously maintain a shared mental model by:
- summarize the current understanding when meaningful progress is made;
- separate confirmed facts, assumptions, interpretations, and open decisions;
- highlight ambiguity, conflicting requirements, missing constraints, and unclear evaluation criteria;
- check whether the inferred objective matches the user's actual intent.
Do not execute, implement, modify, submit, publish, or finalize any consequential output until:
- the relevant decisions, dependencies, and constraints have been resolved;
- the desired outcome and measurable success criteria are explicit;
- major assumptions and trade-offs have been surfaced and accepted;
- the user explicitly confirms that shared understanding has been reached.
Maintain a balance between rigor and efficiency. Be persistent enough to prevent avoidable misunderstandings, but avoid unnecessary interrogation. Prioritize clarity, alignment, and forward progress over exhaustive questioning.
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.
- 11d ago First seen · 54 lines · 286 tokens per session scan A 9392f9a5b2dc
clarify-intent-and-establish-shared-understanding is a skill published in the GitHub repository Inference1/clarify-intent-and-establish-shared-understanding (204 stars, last pushed 17d ago), licensed Apache-2.0. It adds 286 tokens to every session and 933 once invoked, about $0.0014 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-30.
Other skills, from other repositories
capability-discovery
Use when a user asks to find, compare, or evaluate an existing DeepSeek Harness plugin, Skill, MCP server, agent extension, profile, or similar ecosystem capability.
dsh-web-skin-developer
Build a new skin for the dsh-web skin collection (DSH Web GUI) and publish it into the Skin Center — the first-level settings section — scaffold with scripts/dsh-skin-new, author the v2 skin.json manifest plus skin.css token remap (pure asset directory, no package.json, no build step), validate with scripts/dsh-skin…
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
yao-ocr
OCR text recognition expert. ALWAYS invoke this skill when you need to extract text from images or PDFs — including invoices, receipts, ID cards, bank cards, business licenses, tables, handwritten documents, or any visual text content.
yao-workspace
Workspace file I/O expert. ALWAYS invoke this skill when you need to list workspaces, read or write files in a workspace on a remote node, or browse workspace directories. Use this for cross-node file operations — for local sandbox files, use standard filesystem tools instead.
figma-code-connect
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.