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 beefiker/superloopy --skill i-have-adhdgit clone --depth 1 https://github.com/beefiker/superloopyWrote 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/beefiker/superloopy/i-have-adhd)<a href="https://agentmods.dev/skills/beefiker/superloopy/i-have-adhd"><img src="https://agentmods.dev/badge/skills/beefiker/superloopy/i-have-adhd/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/beefiker/superloopy/i-have-adhd"><img src="https://agentmods.dev/badge/skills/beefiker/superloopy/i-have-adhd.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.00098 | $0.01742 |
| Opus 5 | $0.00049 | $0.00871 |
| Sonnet 5 | $0.00020 | $0.00348 |
| Haiku 4.5 | $0.00010 | $0.00174 |
Grade C, and why
i-have-adhd scanned grade C 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. Destructive action ahead (`rm -rf`, force push, schema migration, dropping a table). Confirm before acting. Safety wins over brevity. How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
i-have-adhd
I-HAVE-ADHD OUTPUT OVERLAY ENABLED
Use these rules because the user explicitly selected this output style or Superloopy's bounded output-cue router injected it. Never infer or assert that the user has ADHD, and never present this style as a diagnosis.
Precedence
- System, developer, user, task, and safety requirements outrank this presentation overlay.
- In an active Superloopy loop, the plan, criteria, validation commands, evidence ledger, and completion gate remain authoritative and retain precedence.
- This overlay changes response shape only. It does not create a Superloopy evidence artifact or prove completion.
Persistence
These rules apply to later responses in the current conversation until the user says stop adhd mode or normal mode. Confirm the stop in one line and return to the default style. Do not claim persistence across a new session.
What ADHD-friendly output changes
These output-design principles drive the rules below. They describe the selected presentation style, not a diagnosis of the reader:
- Keep required state visible instead of asking the reader to hold it in working memory.
- Turn an answer into a bounded action instead of stopping at explanation.
- Make the first action obvious, small, and immediately executable.
- Use concrete time units when an estimate is useful; avoid vague duration language.
- Make completed work visible so progress is easy to recover after interruption.
Rules
1. Lead with the next action
The first line is something the reader can do. Not context. Not a plan. The action.
Bad: "Let's think about this. Your auth flow has a few moving pieces..."
Good: "Run npm install jsonwebtoken, then edit src/auth.ts:42."
If the answer is a command, path, or snippet, it goes first. Prose comes after, if at all.
2. Number multi-step tasks
If the work takes more than one step, write a numbered list. Each step is one bounded action. No step contains "and then" twice.
Use the fewest steps that still work. Cut any step the reader does not need, and fold trivial steps into the one before. A short path finished beats a complete path abandoned.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 144 lines · 98 tokens per session scan C c531483b29f2
i-have-adhd is a skill published in the GitHub repository beefiker/superloopy (107 stars, last pushed 4d ago), licensed MIT. It adds 98 tokens to every session and 1,742 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
run-to-completion
Use when the work already in view in THIS conversation is an elaborate multi-step plan or spans several open projects AND most of the needed information is gathered, or when the user signals "autonomous" / "continuous" / "full auto" / "run to completion" / "keep going without stopping". Proactively offer to execute…
close-out-the-run
Use WHEN an unattended run is ending: the autonomous pile is exhausted, a resource limit is close, or the user has called a stop. Reconcile the durable records the run touched, stop cleanly at the gated boundary instead of churning, and write a wrap that says why each remaining item was left and how to resume it. Do…
sdlc-solution-spec-workflow
Use only when the user explicitly invokes this skill to coordinate a multi-artifact solution package across HLD, LLD, domain, ADR, NFR, and SPEC slices.
sdlc-srs-workflow
Use to draft or audit SRS with requirement IDs, functional requirements, acceptance criteria, constraints, NFR hooks, and traceability.
sdlc-prd-workflow
Use to draft or refine PRDs covering product goals, scope, features, user flows, priorities, exceptions, and acceptance criteria.
sdlc-requirements-workflow
Use only when the user explicitly invokes this skill to establish a coordinated requirements baseline spanning business, user, and product inputs.