Borrowing it
Nothing to install: this file belongs to mag123c/toktrack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mag123c/toktrack/main/.claude/skills/clarify/SKILL.mdgit clone --depth 1 https://github.com/mag123c/toktrackWrote 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/mag123c/toktrack/clarify)<a href="https://agentmods.dev/skills/mag123c/toktrack/clarify"><img src="https://agentmods.dev/badge/skills/mag123c/toktrack/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.
<a href="https://agentmods.dev/skills/mag123c/toktrack/clarify"><img src="https://agentmods.dev/badge/skills/mag123c/toktrack/clarify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
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 154 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.
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.00043 | $0.01268 |
| Opus 5.5 | $0.00017 | $0.00507 |
| Sonnet 5.5 | $0.00009 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/clarify — Adaptive Requirements Clarification
Chain (MUST)
| Previous | Current | Next |
|---|---|---|
| Session start | /clarify | Present PLAN inline → /implement |
Core Model
/clarify → Measure complexity → Clear enough?
├─ Yes → Present PLAN inline → /implement
└─ No → Deeper clarify (explore, analyze, DRAFT...)
→ Re-measure → Repeat
Exit condition: "Is this enough info to implement?" — Critical Unknown=0 + remaining items are made visible (Provenance).
Reference Files (load as needed — chaining)
| When | File |
|---|---|
| Tagging provenance on key decisions/assumptions / probe decisions | references/provenance.md |
| Pre-PLAN user confirmation | references/checkpoint.md |
| When document authority/reading order is unclear | references/doc-roles.md |
| Full Deep path procedure | deep/DEEP.md |
| PLAN/DRAFT structure (Lite/Full + Clarify Verdict) | templates/ |
Inline essentials only: probe-don't-tag (if cheaply verifiable, measure instead of tagging), PLAN=intent · WRAP/DECISIONS=fact, do not hide inferences. Details in the references above.
Step 0: Route — Complexity Assessment
Measure complexity internally upon receiving request (do not expose to user).
Complexity Signals
| Signal | LOW | HIGH |
|---|---|---|
| Request length | Short and specific | Long or ambiguous |
| Keywords | "add", "fix", "change" | "design", "migration", "from scratch" |
| Uncertainty | None | "not sure", "how should I" |
| Impact scope | Single file/module | Cross-cutting, multiple services |
| Risk | Low (UI, text) | High (DB, auth, breaking API) |
| Existing patterns | Clearly exist | None or unfamiliar stack |
- LOW → Shallow Path (completed within this file)
- HIGH → Deep Path (see
deep/DEEP.md) - Ambiguous → Start Shallow, monitor escalation conditions
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 157 lines · 43 tokens per session scan A 84c68d7ef5ae
clarify is a skill published in the GitHub repository mag123c/toktrack (196 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,268 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.
Other skills, from other repositories
microservices-architecture
Microservices architecture patterns and best practices. Use when designing distributed systems, breaking down monoliths, or implementing service communication.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
audio-production
Professional audio production for music, podcasts, and sound design. Use when working with audio recording, mixing, mastering, or sound design for any medium.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.