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 anthony-chaudhary/dos-kernel --skill dos-dispatch-loopgit clone --depth 1 https://github.com/anthony-chaudhary/dos-kernelWrote 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/anthony-chaudhary/dos-kernel/dos-dispatch-loop)<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-dispatch-loop"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-dispatch-loop/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/anthony-chaudhary/dos-kernel/dos-dispatch-loop"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-dispatch-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 248 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00049 | $0.04283 |
| Opus 5.5 | $0.00020 | $0.01713 |
| Sonnet 5.5 | $0.00010 | $0.00857 |
| Haiku 4.5 | $0.00005 | $0.00428 |
Grade A, and why
dos-dispatch-loop 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dos-dispatch-loop — the generic dispatch⇄replan cadence
The unattended plan-and-ship loop. It runs
/dos-dispatchrepeatedly and falls to/dos-replanwhen a lane drains, stopping on a typed, kernel-decided condition (not a prose guess). The stop/continue logic is the kernel'sloop_decide.decide— the loop carries counters, the kernel decides. Several loops on disjoint lanes run in parallel, each holding its own lane lease.
The stop conditions are the kernel's, in one place:
- iteration cap — reached
max_iterations(default 10). - drained-twice — a DRAIN after a productive
/dos-replanthat itself followed a DRAIN (the lane is genuinely exhausted). - consecutive-unclear — the dispatch subprocess is failing systematically.
- rate-limited — a usage window is exhausted (don't burn launches).
- launch-failed — a subprocess never started.
- pick-held-invariant — the next unit is held ONLY by a reason a re-dispatch cannot change (draft-class / operator-gated / soak-open / dependency-unmet); re-dispatching it would re-block identically, so honest-STOP + surface the hold.
- pick-cooldown — the next unit was attempted-and-didn't-move inside its cooldown window AND nothing fresher is offerable; re-dispatching it would re-storm a known drain (the ~5%-shipping re-pick loop the bare loop hit).
- not-ratcheting — the OUTER RATCHET (docs/351): the loop has run too many
iterations in a row with no witnessed net gain — the reconcile-VERIFIED
ship-count (Step 3) is not rising, even though each iteration reported SHIPPED.
The loop is running but not improving (the "spinning, narrating progress while
net-shipping nothing real" failure that worsens the longer the loop runs). The
verdict is the kernel's
improveESCALATE, read VERBATIM — not the loop's self-report. Hand the judgment back to a human.
Conditions 6–7 are the docs/207 anti-churn rungs (the loop stops re-picking work
it cannot move); condition 8 is the docs/351 ratchet (the loop stops when it is
moving but not improving — RSI made first-class here, the same improve keep-gate
the /dos-self-improve loop uses, now gating each dispatch iteration's net gain).
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.
- 1mo ago First seen · 297 lines · 49 tokens per session scan A 866f5eb83603
dos-dispatch-loop is a skill published in the GitHub repository anthony-chaudhary/dos-kernel (20 stars, last pushed 21d ago), licensed MIT. It adds 49 tokens to every session and 4,283 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
backlog-capture
Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.
queue-handoff
Use when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going…