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/breakdown)<a href="https://agentmods.dev/commands/emircbngl/claude-adhd-productivity/breakdown"><img src="https://agentmods.dev/badge/commands/emircbngl/claude-adhd-productivity/breakdown/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/breakdown"><img src="https://agentmods.dev/badge/commands/emircbngl/claude-adhd-productivity/breakdown.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.00010 | $0.00163 |
| Opus 5 | $0.00005 | $0.00081 |
| Sonnet 5 | $0.00002 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
breakdown 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 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.
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/task-decomposition.md, then break down the task.
Task: $ARGUMENTS
(If empty, use the Current task in FOCUS.md.)
- Name the finish line in one sentence.
- List 3–6 rough chunks (don't over-engineer).
- Find the first 2-minute physical action and put it in the NOW line of
FOCUS.md. - Write the step list to
FOCUS.mdwith "← you are here" on the current step. - In your reply, show ONLY the next single action — the full list lives in the file so it doesn't recreate overwhelm.
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 · 16 lines · 10 tokens per session scan A 75ae385bc3da
breakdown is a command published in the GitHub repository emircbngl/claude-adhd-productivity (3 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 163 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.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
design
A command that turns an existing plan into a detailed technical design for building the feature.