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-next-upgit 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-next-up)<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-next-up"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-next-up/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-next-up"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-next-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.03098 |
| Opus 5 | $0.00026 | $0.01549 |
| Sonnet 5 | $0.00011 | $0.00620 |
| Haiku 4.5 | $0.00005 | $0.00310 |
Grade A, and why
dos-next-up 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.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dos-next-up — the generic plan-and-ship snapshot
This is the baseline screenplay DOS ships, not a prerequisite. It drives the kernel syscalls (
verify,gate) against any repo whose layout lives indos.toml. It names no host directory, no host lane, and no host commit convention — every host specific comes fromdos doctor --json(paths/lanes, via WCR) ordos.toml [stamp](the ship grammar, via SCV). Copy it into your own skills dir, pointdosat your workspace, and it runs.
The shape is domain-free: discover the layout → walk the plans → audit each pick against the truth syscall → render a packet → gate the empty case. The policy (which lanes, which plan grammar, where output lands) is data the screenplay reads, never literals it hardcodes.
Inputs
--scope <name>(repeatable, optional) — narrow candidates to one lane (a name from the active[lanes]taxonomy) or one plan id. Omitted = all plans.--limit <N>(optional, default 5) — how many top picks to render.
Step 0 — Discover the workspace layout (one call)
Run the doctor verb and read the result. This is the WCR on-ramp: every path/lane below comes from here, never a literal.
dos doctor --workspace . --json
Parse the JSON object. The fields you use:
paths.plans_glob— the glob to walk for plan docs (whatever the workspace declared). Use this value; never assume a fixed plans directory.paths.next_packets— where the rendered packet is written (the configured output dir;.dos/verdictsunder the generic default).lanes.concurrent/lanes.exclusive/lanes.trees— the active lane taxonomy, if you need to group picks by lane or honor a--scope.stamp— the active ship-subject grammar (informational;dos verifyapplies it for you — you never grep subjects yourself).
If git is false, warn the operator: dos verify's git rung has no history to
read, so every pick will report source="none" unless a registry exists.
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 · 236 lines · 53 tokens per session scan A 872f4991f90a
dos-next-up is a skill published in the GitHub repository anthony-chaudhary/dos-kernel (19 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 3,098 once invoked, about $0.0003 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
squads-cli
Squads CLI — operate your AI workforce through the loop; intent in, reviewed work out. TRIGGER when running squads, dispatching agents, triaging the inbox, reading/writing memory, recording feedback, or checking status/usage.
aigon-next
Suggest the most likely next workflow action based on current context.
aigon-board
Show Kanban board or list view.
gh
You have access to gh (GitHub CLI) for repository and project management.
aigon-feature-prioritise
Prioritise feature - assigns ID, moves to backlog.
aigon-feature-reset
Reset feature - remove worktrees, branches, state, and return lifecycle to backlog.