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 agentmods add skills/anthony-chaudhary/dos-kernel/dos-replan-loopnpx skills add anthony-chaudhary/dos-kernel --skill dos-replan-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-replan-loop)<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/dos-replan-loop"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/dos-replan-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 | $0.00044 | $0.01724 |
| Opus 5 | $0.00022 | $0.00862 |
| Sonnet 5 | $0.00009 | $0.00345 |
| Haiku 4.5 | $0.00004 | $0.00172 |
Grade A, and why
dos-replan-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 4d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dos-replan-loop — the generic recurring planning sweep
The thin loop. It is mostly sequencing: run
/dos-replan, run an optional auto-commit/release contract, increment a counter, schedule the next wakeup, and stop at the iteration cap. The one thing it must get right generically is the release guard — it reads the workspace's trunk from config, not a hardcoded branch name. (This repo's trunk ismaster, notmain— exactly the kind of host fact the guard must read, not assume.)
Inputs
--interval <seconds>(optional, default 600 — 10 minutes).--max-iterations <N>(optional, default 20).
Step 1 — First entry
Set the iteration counter to 1. Record the pre-existing dirty state of the tree
(so the auto-commit guard can tell what this sweep changed). Invoke the
/dos-replan Skill.
Step 2 — After /dos-replan finishes: the guarded release contract
If /dos-replan made garden-only writes, optionally commit + release them — but
only behind the guard. The guard reads the trunk from config, not a literal:
dos doctor --workspace . --json
There is no trunk field in the doctor report today (it is a host fact); resolve
it the generic way: git symbolic-ref --short refs/remotes/origin/HEAD (the
remote's default branch). Fail closed: if that cannot be resolved (no
origin/HEAD — common in fresh clones / CI checkouts), treat the trunk as
UNKNOWN and skip the release entirely (record the sweep only). Do NOT fall
back to "the current branch" — that would make the on-trunk check below trivially
true on any branch and let an auto-commit proceed off-trunk. Then the guard fires
only when ALL hold:
- the trunk is positively known (resolved above, not UNKNOWN), AND HEAD is
on it (the resolved default branch —
masterhere,mainelsewhere; never hardcode either). - the working-tree changes are docs/state-only (the replan queue + cooldown state, nothing in code).
- there is something to commit (a productive sweep).
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.
- 4d ago First seen · 129 lines · 44 tokens per session scan A 727088ea60c7
dos-replan-loop is a skill published in the GitHub repository anthony-chaudhary/dos-kernel (19 stars, last pushed 11d ago), licensed MIT. It adds 44 tokens to every session and 1,724 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
takt
TAKT ワークフローエンジン。Agent Team を使ったマルチエージェントオーケストレーション。ワークフロー YAML（steps / initialstep）に従ってマルチエージェントを実行する。.
takt
TAKT ワークフローエンジン。codex exec でサブエージェントを起動し、ワークフロー YAML（steps / initialstep）に従って マルチエージェントオーケストレーションを実行する。.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
Research Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.