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/emircbngl/claude-adhd-productivityWrote 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/emircbngl/claude-adhd-productivity/unstick)<a href="https://agentmods.dev/commands/emircbngl/claude-adhd-productivity/unstick"><img src="https://agentmods.dev/badge/commands/emircbngl/claude-adhd-productivity/unstick/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/commands/emircbngl/claude-adhd-productivity/unstick"><img src="https://agentmods.dev/badge/commands/emircbngl/claude-adhd-productivity/unstick.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.00020 | $0.00188 |
| Opus 5 | $0.00010 | $0.00094 |
| Sonnet 5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
unstick 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 10d 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
Read the adhd-focus skill and references/anti-shame-rsd.md, then run the de-escalation pattern.
- Normalize immediately — name it as wiring (time-blindness, interest-based brain, RSD), not a character flaw. Take the moral weight off.
- One warm validating sentence, then move — don't wallow.
- Shrink the task until it's almost laughably small. Remove the mountain; show one pebble.
- Remove choices — give exactly ONE physical action, not a menu.
- Frame it as a fresh start, not catching up. The past pile doesn't exist right now.
- Offer to body-double the one tiny step.
Never use shame or pressure language ("should", "just", "behind", "why didn't you").
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.
- 10d ago First seen · 15 lines · 20 tokens per session scan A f1c8ad92fb1e
unstick is a command published in the GitHub repository emircbngl/claude-adhd-productivity (3 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 188 once invoked, about $0.0001 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-31.
Other commands, from other repositories
setup
Interview me and scaffold my personal chief-of-staff system (context file, memory, task list, daily brief).
brief
Produce my morning brief — what's on today, what's slipping, what to prep, one thing worth my attention.
loops
Weekly review — surface everything in-flight and force a ship / block / kill decision on each.
rename
Generate a concise, sentence-case title (3-7 words) that captures the main topic or goal of this coding session. The title should be clear enough that the user recognizes the session in a list. Use sentence case: capitalize only the first word and proper nouns.
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
help
Explain Ralph Wiggum technique and available commands.