A workflow for continuing Cladding onboarding after a user answers a pending product question.

Use it to prepare and apply an onboarding clarification, show proposed changes when review is needed, and finish only when Cladding reports completion.

It prevents the system from guessing answers and ensures the user's response is carried through the required review process.

clarify — Skill for Claude Code and Codex by qwerfunch/cladding

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 qwerfunch/cladding --skill clarify

Clone the repo

git clone --depth 1 https://github.com/qwerfunch/cladding

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/qwerfunch/cladding/clarify/github.svg)](https://agentmods.dev/skills/qwerfunch/cladding/clarify)

Your own site

<a href="https://agentmods.dev/skills/qwerfunch/cladding/clarify"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/clarify/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/qwerfunch/cladding/clarify"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/clarify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 347 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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.00347
Opus 5.5	$0.00023	$0.00139
Sonnet 5.5	$0.00011	$0.00069
Haiku 4.5	$0.00006	$0.00035

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

Security

Grade A, and why

clarify 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.

plugins/antigravity/skills/clarify/SKILL.md · 19 lines

What it actually says

Cladding clarify

Use this workflow only for an answer contained in a new user message after Cladding displayed the pending question. Never infer, synthesize, or reuse an answer from an initialization turn. If no new user answer exists, stop without calling either clarify tool.

Use this workflow only after Cladding initialization returned a pending question and the user has answered it.

Call clad_prepare_clarify with the user's answer verbatim.
Read the returned prompt, current state, and artifacts. Draft the structured refinement required by clad_clarify using the current host model.
Call clad_clarify with the same answer, the one-time token, and the draft.
Ask nextQuestion verbatim when one remains.
If the result is needs_review, show the proposal diffs for every pendingReview target and wait for explicit user approval. Only then call clad_resolve_onboarding_review with the approved targets. Never describe onboarding as complete while review remains.
Report completion only when the returned status is done.

Do not run clad clarify in a shell from an AI host. Do not use MCP sampling. Never answer a product question on the user's behalf. A stale, malformed, replayed, or answer-mismatched apply request is a no-op and must be prepared again.

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.

1mo ago First seen · 19 lines · 57 tokens per session scan A 5d08bbb82125

Subscribe to this mod's changes

clarify is a skill published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 347 once invoked, about $0.0002 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.

Claude Code ai-coding claude-code-plugin codex-cli cursor-ide drift-detection

maintaining-windows-health

Hands-on playbook for Windows 11 disk cleanup, dev-machine optimization, and proactive health alerting. Use when the PC is full or slow, when a BSOD / Kernel-Power 41 / crash dump / commit-memory pressure happened, when the user asks to free disk space, audit storage, set up disk/memory alerts, or restore the same…

CodeAlive-AI/ai-driven-development · 191 tokens

prompt-engineering

Universal prompt engineering techniques for any LLM. Use when crafting, optimizing, or reviewing prompts for AI models. Triggers on requests like "improve this prompt", "write a system prompt", "optimize my instructions", "help me prompt engineer", "audit this prompt", "review my prompt", or when building agentic…

CodeAlive-AI/ai-driven-development · 76 tokens

installing-cli-tools

Install, upgrade, configure, and verify developer CLI tools safely. Use when a user asks to install a new CLI, command-line app, SDK tool, package-manager binary, GitHub release binary, language runtime tool, or AI/vendor CLI; configure shell PATH/completions; run first login; set API keys, tokens, or env variables…

CodeAlive-AI/ai-driven-development · 94 tokens

repo-activity-summary

Summarize a repository's recent engineering activity from git history — technologies, work types, churn hotspots, contributor patterns, and velocity. Use when asking "what has this repo been working on", "is this project active", "who contributes what", "where are the hotspots", or before onboarding onto an unfamiliar…

CodeAlive-AI/ai-driven-development · 70 tokens

clipboard

Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".

CodeAlive-AI/ai-driven-development · 36 tokens

grok-cli

Delegate bounded tasks to Grok Build from a supervising agent such as Codex. Use when the user asks Grok to investigate, review, implement, or provide another perspective, or when a distinct coding agent would materially help. Includes a background ACP client for progress, follow-up prompts, permissions, and…

scarletkc/agents · 66 tokens