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-goal-fleetgit 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-goal-fleet)<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-goal-fleet"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-goal-fleet/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-goal-fleet"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-goal-fleet.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 Tool Misuse · line 238 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00051 | $0.05024 |
| Opus 5 | $0.00026 | $0.02512 |
| Sonnet 5 | $0.00010 | $0.01005 |
| Haiku 4.5 | $0.00005 | $0.00502 |
Grade A, and why
dos-goal-fleet 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 10d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dos-goal-fleet — wave-launched self-stopping goal workers, witnessed not narrated
A fleet that trusts each worker's "I'm done" is a fleet of silent fails. The move this skill makes is the one the whole substrate exists for: a worker's "the goal is met" is a claim with a byte-author, and the byte-author is the judged worker. So each child's stop is gated on
dos-goal-gate— it cannot declare done until a witness it did not write (git ancestry, an effect read-back) corroborates the goal's effects. The fleet launches the leaves; the kernel decides which ones actually landed. The skill narrates; it never rules.
Take an operator-supplied context describing several independent objectives, turn each into ONE headless worker armed with a single goal, and fire them in waves sized to whatever seat pool the host exposes — so the launch is load-balanced and no single account walls. This is the fan-out analogue of two sibling skills:
dos-goal-gateis one self-stopping leaf — a single agent whose "done" is grounded.dos-goal-fleetarms many such leaves at once. Each child runs the goal-gate discipline; this skill is the launcher and the rollup around them.dos-witness-claimis the fold — believing only the confirmed effects when many workers' results converge. Step 5 here is that fold, applied to the fleet's per-instance outcomes.
The shape is domain-free: decompose into independent goals → price the wave into
its serial/concurrent partition → arbitrate co-launch safety → wave-launch one
self-stopping child per goal → witness every claimed ship → roll up. Pricing the
partition is the default first move, not an optional optimization: concurrency is
earned per disjoint tree, never assumed for the wave. The policy (which lanes,
which plan grammar, how the host rotates accounts, which model a child runs) is
data read from dos doctor --json / dos.toml and from the host's own launch
convention — never a literal this screenplay hardcodes. A shipped generic skill names no host (the
litmus); the host-specific launch verb is a seam you fill in Step 3.
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.
- 10d ago First seen · 349 lines · 51 tokens per session scan A c9f9408d658b
dos-goal-fleet is a skill published in the GitHub repository anthony-chaudhary/dos-kernel (19 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 5,024 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.