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-supervise-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-supervise-loop)<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-supervise-loop"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-supervise-loop.svg" alt="Measured on agentmods" 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.00043 | $0.03264 |
| Opus 5 | $0.00022 | $0.01632 |
| Sonnet 5 | $0.00009 | $0.00653 |
| Haiku 4.5 | $0.00004 | $0.00326 |
Grade A, and why
dos-supervise-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 7d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dos-supervise-loop — the generic worker-population supervisor
The init/PID-1 of a dispatch fleet. It keeps
--targetworker dispatch-loops alive across the lane roster: each tick it counts live lane leases, classifies each worker's liveness, and fills the roster up to target by launching one/dos-dispatch-loopper free admissible lane. The what to do is a typed kernel verdict —dos loopemits a spawn/reap/flag plan; this skill only carries it out. It reaps a worker ONLY when the kernel says STALLED, never a healthy one, and it FLAGs a SPINNING worker to the operator rather than killing it (acting on a spin is not the supervisor's job).
The supervisor's whole contract is one rule the kernel owns: the population is
filled from the plan, not from a guess. A tick is gather evidence → ask dos loop → carry out spawn/reap/flag. The four dispositions are the kernel's:
- SPAWN — a free, admissible lane below target: launch one worker on it.
- REAP — a STALLED lease: scavenge it so the lane is free to refill.
- HOLD — an ADVANCING (or alive-counted SPINNING) worker: leave it alone.
- FLAG — a SPINNING worker (advisory) or an excess over target: surface it, do not kill it.
Inputs
--target <N>(default 1) — the desired live-worker population. The kernel caps the achievable population at the admissible count (how many roster lanes can simultaneously hold a worker given their disjointness); a--targetabove that yields a TARGET_UNREACHABLE verdict naming the fix.--max-concurrency <N>(optional, docs/283) — the derived-claim concurrency budget. On a DYNAMIC-CLAIM workspace (concurrent = [], where a lane is a HANDLE whose disjointness is enforced per-pick at acquire time, not by a fixed tree), the static admissible count is 1, so a--targetabove 1 is structurally unreachable. Declaring this budget lets the supervisor keep up to N workers alive on a fungible auto-pick handle WITHOUT pre-enumerating N disjoint trees — the arbiter still narrows each worker's per-pick claim at its Step 0. Declare ONE number, not N trees. Set it standing indos.toml [supervise] max_concurrency, or pass--max-concurrencyfor a one-off run. Off by default (admissible stays the static disjoint-lane count — byte-for-byte today's).--interval <seconds>(long default) — the wakeup cadence between ticks. A supervisor wakes rarely; it is a watchdog, not a busy-loop.--max-ticks <N>(optional) — stop after N ticks. Omit for an open-ended run that stops only on an operator interrupt.
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.
- 7d ago First seen · 237 lines · 43 tokens per session scan A 2d4e6dfb73c0
dos-supervise-loop is a skill published in the GitHub repository anthony-chaudhary/dos-kernel (19 stars, last pushed 13d ago), licensed MIT. It adds 43 tokens to every session and 3,264 once invoked, about $0.0002 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-30.
Other skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
My Skill
Content here.
aigon-feature-code-review
Review feature - code review with fixes by a different agent.
aigon-feature-create
Create feature - creates spec in inbox.
code-tour
Maintain docs/code-tour.md — the annotated guided reading of Aigon's core logic. Use when you have changed code the tour quotes, added a subsystem a new reader would need, or the user says "update the code tour", "the tour is stale", "add X to the code tour", or asks to review/refresh the code examples doc.
aigon-feature-now
Fast-track feature - create + setup + implement in one step.