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 agentmods add skills/umputun/cc-thingz/clarifynpx skills add umputun/cc-thingz --skill clarifygit clone --depth 1 https://github.com/umputun/cc-thingzWrote 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/umputun/cc-thingz/clarify)<a href="https://agentmods.dev/skills/umputun/cc-thingz/clarify"><img src="https://agentmods.dev/badge/skills/umputun/cc-thingz/clarify.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.00091 | $0.01811 |
| Opus 5 | $0.00046 | $0.00905 |
| Sonnet 5 | $0.00018 | $0.00362 |
| Haiku 4.5 | $0.00009 | $0.00181 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarify
Handle user confusion by verifying intent, explaining actual behavior, and determining if there's a real issue.
Primary goal: Clarify and explain, not fix. Most confusion stems from misunderstanding or forgetting, not from bugs.
Activation Triggers
- "confused", "I'm confused", "this is confusing"
- "I don't understand", "doesn't make sense", "makes no sense"
- "wait, shouldn't it...", "but I thought..."
- "why is this happening", "why does this..."
- "I expected X but got Y"
- "this is wrong", "something's off"
- frustration signals, contradictory statements
- questions that reveal misconceptions about system behavior
Important Context
Users often:
- Work on multiple projects in parallel and may confuse behaviors between them
- Forget how things were implemented especially after time away
- Have outdated mental models based on old versions or different projects
- Mix up similar concepts from different codebases or frameworks
But also:
- Users are experienced developers - their instincts are often correct
- Real bugs exist - about half of confusion cases point to actual issues
- User expectations are reasonable - if something feels wrong, investigate thoroughly
Do not assume either way. Investigate before concluding. Both outcomes are equally valid:
- User misremembered/mixed things up -> clarify with evidence
- System has a genuine issue -> proceed to plan mode for fix
Workflow
Phase 1: Identify the Confusion
- Extract the core question - What specifically is the user asking about?
- Identify the expectation - What did the user expect to happen?
- Identify the reality - What is actually happening?
- Locate the gap - Where is the misalignment?
- Consider context mixing - Could user be thinking of a different project/feature?
Categories of confusion:
- Memory gap - user forgot how it works, needs a reminder
- Project mixing - user confused this with another project they're working on
- Outdated mental model - user's understanding is based on old behavior
- Architectural - misunderstanding system design, component relationships, data flow
- Behavioral - expecting different runtime behavior than what occurs
- Configuration - settings not producing expected results
- Documentation - docs don't match implementation or are unclear
- Conceptual - misunderstanding underlying concepts or patterns
- Implementation - code doesn't work as assumed
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.
- 6d ago First seen · 215 lines · 91 tokens per session scan A 3c98ff57c98b
clarify is a skill published in the GitHub repository umputun/cc-thingz (466 stars, last pushed 12d ago), licensed MIT. It adds 91 tokens to every session and 1,811 once invoked, about $0.0005 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
plugin
Manage Claude Code plugins — add marketplaces, install, update, remove, list. Use when installing plugins, checking status, or managing the registry.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
flow-next-guide
Recommend the smallest sufficient flow-next workflow from the starting state. Stateless router. Use when unsure which command or stage applies next.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).