dos-unstick

dos-unstick is a skill for Claude Code from anthony-chaudhary/dos-kernel. It costs 49 tokens per session (1,296 once invoked), scanned A, original, MIT.

A read-only review of blocked or drained runs, grouping repeated problems into common causes. It then suggests one structural fix for each recurring cause.

In plain words
What is it for?
Use it to examine recent runs or a time window, set a minimum recurrence threshold, rank causes by recurrence and delay cost, and surface proposed fixes.
Why use it?
It helps teams address the reason work repeatedly stalls instead of applying one-off fixes to individual runs.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dos-kernel plugin — 18 skills, 3 hooks, 1 MCP server shipped together

Good fit Use it to examine recent runs or a time window, set a minimum recurrence threshold, rank causes by recurrence and delay cost, and surface proposed fixes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anthony-chaudhary/dos-kernel/dos-unstick
Install

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.

Any agent
npx skills add anthony-chaudhary/dos-kernel --skill dos-unstick
Clone the repo
git clone --depth 1 https://github.com/anthony-chaudhary/dos-kernel

Made for: Claude Code.

Or install dos-kernel, the plugin that ships this one along with the rest of its 18 skills, 3 hooks, 1 MCP server.

Wrote 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.

agentmods badge for dos-unstick

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-unstick/github.svg)](https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-unstick)
Your own site
<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-unstick"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-unstick/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.

agentmods 80×15 button for dos-unstick

Your own site · 80×15
<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-unstick"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-unstick.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,296 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01296
Opus 5 $0.00024 $0.00648
Sonnet 5 $0.00010 $0.00259
Haiku 4.5 $0.00005 $0.00130

Measured 9d ago against content hash d9b650b12828, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

dos-unstick 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.

claude-plugin/skills/dos-unstick/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

dos-unstick — the recurring-blocker remediation sweep

Stop the cause, not the instance. A one-off unblock fixes today's stall; /dos-unstick asks the different question — what keeps blocking progress across runs, and what one change would unblock it? It mines the run archive, normalizes every blocker to a canonical cause key, clusters the recurring ones, ranks by recurrence × measured stall-cost, and proposes a structural fix per cluster. Read-only; it writes no code and surfaces findings, never acts.

The shape: mine the trail → key each blocker → cluster the recurring ones → rank → propose a structural fix → surface. The recurrence fold is the kernel's (recurring_wedge); the cause TAXONOMY is [reasons] data — a host adds a cause by declaring a reason, never by editing this skill.

Inputs

  • --runs <N> (optional) — how many most-recent runs to sweep (default: a recent window). --since <Nd|Nh> overrides with a time window.
  • --min-recurrence <N> (optional) — a cause is "recurring" at N+ distinct runs (default 2 — the recurring_wedge DEFAULT_MIN_RECURRENCE).

Step 0 — Discover the layout + the cause taxonomy

dos doctor --workspace . --json

Read paths.runs (the run-archive dir to sweep) and run dos man wedge to read the closed reason vocabulary — the canonical cause keys this workspace knows. Use these; never hardcode a run path or a cause string. A cause the workspace cares about is a declared [reasons] entry, surfaced by dos man wedge.

dos man wedge

Step 1 — Mine the run-archive trail

Read the run records under paths.runs (read each once, sequentially — no tailing/polling, the very anti-pattern this sweep exists to surface). For each run that STOPPED on a BLOCKED / DRAIN / STALLED outcome, capture: the run id, the iteration, the blocker text, and the measured stall cost ($/wall) if recorded.

No host evidence reader is wired by default. A host that curates a postmortem stream or a hand-ranked next-hits file can expose it as a dos.evidence_sources driver hook; the generic sweep reads only the run-archive verdicts. log a one-line note when a host evidence source is not consulted — no silent gap (the /dos-dispatch-loop discipline).

Read the full file on GitHub · 109 lines

Changes

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.

  1. 9d ago First seen · 109 lines · 49 tokens per session scan A d9b650b12828

Subscribe to this mod's changes

dos-unstick is a skill published in the GitHub repository anthony-chaudhary/dos-kernel (19 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,296 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.