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-dispatchgit 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)<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-dispatch"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-dispatch/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"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-dispatch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 176 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.
- high Rogue Agent · line 179 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.00056 | $0.02738 |
| Opus 5.5 | $0.00022 | $0.01095 |
| Sonnet 5.5 | $0.00011 | $0.00548 |
| Haiku 4.5 | $0.00006 | $0.00274 |
Grade A, and why
dos-dispatch 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dos-dispatch — the generic chained snapshot→ship cycle
The concurrency-safe dispatch. It chains
/dos-next-up(the packet) to a ship, but first takes a lane lease through the admission kernel so several dispatches on disjoint lanes run in parallel without editing the same files. The "may I run on this lane" decision is the kernel's (dos arbitrate), not inline prose. Every path/lane comes fromdos doctor --json; nothing is hardcoded.
The shape: discover → take a lane → snapshot → gate → ship → archive. The
lane taxonomy and the run-dir location are data ([lanes], [paths]); the
admission and the gate verdict are kernel syscalls.
Inputs
--lane <name>(optional) — the lane to dispatch on (a name from the active[lanes]). Omitted = a bare auto-pick: the arbiter picks a free lane from theautopickladder.--leases <json>(optional) — the live leases other dispatches hold, as a JSON list of{lane, lane_kind, tree}(the arbiter keys exclusivity onlane_kind, so include it —cluster/keyword/global). In a real loop these come from a status query; for a single dispatch this is usually[].
Step 0 — Discover the layout + the lane taxonomy
dos doctor --workspace . --json
Read lanes (the taxonomy), paths.next_packets (packet output), and
paths.runs (the run dir to archive under). Use these; never hardcode a lane
name or a run path.
Step 1 — Take a lane lease (the admission kernel)
Ask the kernel whether this dispatch may run on the requested lane, given the live leases. The arbiter runs the tree-disjointness algebra over the lanes' declared trees — two dispatches on disjoint trees both ADMIT; overlapping trees COLLIDE.
dos arbitrate --workspace . --lane <LANE> --kind cluster --leases '<LIVE_LEASES>'
Read the LaneDecision JSON: {outcome, lane, tree, reason, free_clusters, …}.
outcome: "acquire"→ admitted.laneis the lane to run on (may differ from the request when auto-pick reassigned it);treeis its file tree. Proceed.outcome: "refuse"→ not admitted.reasonexplains why;free_clusterslists lanes you could pick instead. Stop (or retry on a free lane). Do not force —--forceis an operator-only override, not an automation default.
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 · 213 lines · 56 tokens per session scan A be802f8f7d37
dos-dispatch is a skill published in the GitHub repository anthony-chaudhary/dos-kernel (20 stars, last pushed 21d ago), licensed MIT. It adds 56 tokens to every session and 2,738 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…