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/effort-control-for-token-intensive-work)<a href="https://agentmods.dev/commands/runnithan/claudex-setup/effort-control-for-token-intensive-work"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/effort-control-for-token-intensive-work.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.00303 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
effort-control-for-token-intensive-work 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 8d 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
Use /effort to Match Thinking Depth to Task Risk
TL;DR
/effort sets how deeply the model reasons: low is fast and shallow, the default is high, and extra-high/max are slower but markedly more careful, switch up for risky or complex changes, back down for routine ones, and check the cost with /usage afterwards.
Why it matters
Effort is a per-task dial, not a set-and-forget setting. Running max effort on trivial edits wastes time and tokens; running low effort on intricate logic ships missed edge cases. Deliberately matching the dial to the blast radius of the change gets both speed and care where each belongs.
How to apply
Before a risky change (migrations, auth, concurrency, tricky refactors), run /effort and pick extra-high or max; drop back to the default for everyday work. Pair with /usage after heavy runs to learn what each effort level actually costs on your tasks, so the choice becomes calibrated rather than guessed.
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.
- 8d ago First seen · 25 lines · 0 tokens per session scan A e066c697bb6e
effort-control-for-token-intensive-work is a command published in the GitHub repository runnithan/claudex-setup (1 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 303 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.
security-review
A security review procedure based on CWE, a list of common software weaknesses, and STRIDE, a method for identifying threats to a system.
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
refactor
Analyze code for SOLID violations and suggest targeted improvements.