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-gategit 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-gate)<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-goal-gate"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-goal-gate/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-gate"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-goal-gate.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.00054 | $0.04260 |
| Opus 5 | $0.00027 | $0.02130 |
| Sonnet 5 | $0.00011 | $0.00852 |
| Haiku 4.5 | $0.00005 | $0.00426 |
Grade A, and why
dos-goal-gate 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dos-goal-gate — gate "I'm done" on a witness, not on self-report
A completion condition the agent checks against its own narration is the exact failure DOS exists to fix. When an agent decides "the goal is met" by re-reading what it just wrote, the part deciding ground truth is the part being judged — that is consistency, not grounding (docs/138). This skill never decides done-ness by re-reading the transcript. It turns the goal into a set of checkable EFFECT claims, then wires the Stop decision so the agent cannot stop until a read-back whose byte-author is not the agent (git ancestry, an OS exit code, a fresh state read) corroborates each effect. The kernel decides; the skill narrates.
The shape is domain-free: state the goal as effects → wire the Stop gate →
on each stop, witness every effect → stop only when all are corroborated. The
policy (which plan grammar, which lanes, where state lives) is data read from
dos doctor --json, never literals this screenplay hardcodes.
Why this is not just "ask the model if it's done." A harness stop-condition ("keep going until X") is evaluated by a model reading the session — so a confident, fluent narration of an X that the world does not corroborate ends the work early (the silent fail of docs/177). The gate below replaces that judgment with a verdict over evidence the agent did not write: a phase is done when git says a commit backs it, not when the agent says it committed; a file exists when a fresh read finds it, not when the agent says it wrote it.
When to use this (and when not)
- Use it when a single agent self-paces toward a stated goal and you want its
"done" to be unfalsifiable-by-narration — a
/loopworker, a self-stopping task agent, or any run where the operator stated a completion condition. - Use
dos-witness-claiminstead when many workers' results are folded at aparallel()/pipeline()barrier — that skill is the fan-out fold analogue; this one is the single-agent self-stop analogue. Same witness discipline, different site. - This is advisory (a PDP, not a PEP — docs/99). It computes a Stop verdict and lets the runtime act on it via the user-owned hook seam. It blocks a false done; it never blocks a true one, and it never enforces beyond the Stop hook.
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 · 298 lines · 54 tokens per session scan A 3fe45ea2806b
dos-goal-gate is a skill published in the GitHub repository anthony-chaudhary/dos-kernel (19 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 4,260 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
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
My Skill
Content here.
claude-code-expert
Especialista profundo em Claude Code - CLI da Anthropic. Maximiza produtividade com atalhos, hooks, MCPs, configuracoes avancadas, workflows, CLAUDE.md, memoria, sub-agentes, permissoes e integracao com ecossistemas.
aigon-feature-code-review
Review feature - code review with fixes by a different agent.
aigon-feature-create
Create feature - creates spec in inbox.
aigon-feature-spec-review
Review feature spec - improve the spec itself before implementation.