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.
git clone --depth 1 https://github.com/runnithan/claudex-setupWrote 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/commands/runnithan/claudex-setup/custom-clarifying-questions-slash-command)<a href="https://agentmods.dev/commands/runnithan/claudex-setup/custom-clarifying-questions-slash-command"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/custom-clarifying-questions-slash-command.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.00000 | $0.00349 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
custom-clarifying-questions-slash-command 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 7d 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
Build a Custom Slash Command That Asks Clarifying Questions First
TL;DR
Package the "ask before you build" habit into a reusable custom slash command: it captures the task, asks ~5 clarifying questions, drafts a plan, and waits for approval before executing.
Why it matters
Tristen O'Brien reports a ~43% output-quality improvement from a custom command that forces clarity up front. The win isn't the questions themselves, it's making the behavior repeatable as a one-word command instead of re-typing the spec-developer preamble every session. This turns the existing [[spec-developer-workflow-with-clarifying-questions]] prompt into reusable infrastructure.
How to apply
Create .claude/commands/<name>.md (e.g. clarify.md) whose body instructs Claude to:
- Restate the task in its own words.
- Ask 5+ clarifying questions covering scope, constraints, edge cases, and the definition of done.
- Wait for answers, then produce a plan.
- Pause for explicit approval before writing any code.
Invoke it with /clarify <task> at the start of any non-trivial work. Pair with [[plan-mode-before-every-nontrivial-change]] so the plan is reviewable before execution.
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.
- 7d ago First seen · 27 lines · 0 tokens per session scan A 631b6c34f008
custom-clarifying-questions-slash-command is a command published in the GitHub repository runnithan/claudex-setup (1 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 349 tokens. 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-31.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
refactor
Analyze code for SOLID violations and suggest targeted improvements.
factcheck
Verify BibTeX entries and cited claims against DBLP and web sources. Checks author names, venues, years, and specific numerical claims.
generate-tests
Generate comprehensive tests for specified code.