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 jhlee0409/all-for-claudecode --skill clarifygit clone --depth 1 https://github.com/jhlee0409/all-for-claudecodeWrote 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/jhlee0409/all-for-claudecode/clarify)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/clarify"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/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/jhlee0409/all-for-claudecode/clarify"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/clarify.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.00014 | $0.00918 |
| Opus 5 | $0.00007 | $0.00459 |
| Sonnet 5 | $0.00003 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade B, and why
afc:clarify scanned grade B with 1 finding 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
!`cat .claude/afc.config.md 2>/dev/null || echo "[CONFIG NOT FOUND] .claude/afc.config.md not found. Run /afc:init first — abort if missing."` How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:clarify — Resolve Spec Ambiguities
Identifies ambiguous or incomplete areas in spec.md and resolves them through user questions. Answers are applied as inline updates to spec.md.
Arguments
$ARGUMENTS— (optional) focus on a specific area (e.g., "security", "performance", "UI flow")
Project Config (auto-loaded)
!cat .claude/afc.config.md 2>/dev/null || echo "[CONFIG NOT FOUND] .claude/afc.config.md not found. Run /afc:init first — abort if missing."
Execution Steps
1. Load Spec
- Read
.claude/afc/specs/{feature}/spec.md— stop if not found - If a
[NEEDS CLARIFICATION]section exists, process it first - Quickly check existing codebase for related patterns
2. Scan for Ambiguities
Scan across 10 categories:
| # | Category | What to find |
|---|---|---|
| 0 | Necessity | Is this feature truly needed? Does it already exist? Is the cost justified by the benefit? |
| 1 | Feature scope | Features with unclear boundaries |
| 2 | Domain/data | Incomplete entity relationships or field definitions |
| 3 | UX flow | Missing user journey steps |
| 4 | Non-functional quality | Performance/security requirements without numeric targets |
| 5 | External dependencies | APIs or libraries needing clarification |
| 6 | Edge cases | Undefined boundary conditions |
| 7 | Constraints/tradeoffs | Mutually incompatible requirements |
| 8 | Terminology consistency | Same concept with different names |
| 9 | Completion criteria | Success criteria that cannot be measured |
| 10 | Residual placeholders | TODO/TBD/??? |
These categories serve as a comprehensive checklist, not a rigid classification. Adapt to the project's domain — skip categories irrelevant to the project type (e.g., skip 'UX flow' for CLI tools) and add domain-specific categories if needed (e.g., 'regulatory compliance' for healthcare/fintech projects).
3. Generate and Present Questions
- Generate questions ranked by their impact on spec quality — how much would the answer change the spec's direction or completeness? Present the most impactful questions first. The number of questions should match the actual ambiguity level: deeply ambiguous specs may need more questions, while mostly-clear specs need fewer. Do not artificially cap at a fixed number, but keep the set focused and avoid overwhelming the user (aim for the minimum needed to resolve critical ambiguities).
- Present one at a time via AskUserQuestion:
- Use multiple choice when possible (2-4 options)
- Include the meaning/impact of each option
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.
- 9d ago First seen · 88 lines · 14 tokens per session scan B 6c419e6ed13b
afc:clarify is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 918 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
orchestrator-lanes
A file-based project-management playbook for a specific Claude Code development orchestrator. It organizes work into lanes, plans, dependency steps, validation phases, and shipping stages.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
investigate
Systematic root-cause debugging: find the cause before writing any fix.