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/stable-releasenpx skills add anthony-chaudhary/dos-kernel --skill stable-releasegit 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/stable-release)<a href="https://agentmods.dev/skills/anthony-chaudhary/dos-kernel/stable-release"><img src="https://agentmods.dev/badge/skills/anthony-chaudhary/dos-kernel/stable-release.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.00081 | $0.05089 |
| Opus 5 | $0.00041 | $0.02544 |
| Sonnet 5 | $0.00016 | $0.01018 |
| Haiku 4.5 | $0.00008 | $0.00509 |
Grade A, and why
stable-release 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 5d 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stable Release — a named channel on top of rolling /release (DOS)
/release ships a rolling tag (vX.Y.Z) whenever DOS lands user-visible change.
That tag promises "this commit merged" — it does not promise "the substrate
was provably trustworthy here." This skill adds a second, less-frequent channel
that does make that promise.
A stable release is a promotion of an already-shipped commit, not a new
build. No new version is minted. No new wheel or zip is produced. The gate is
read at promote time, frozen into an evidence file, and a second annotated tag
(stable/<codename>) is pinned on the same commit.
This is the DOS adaptation of
job's stable-release skill. job gates on apply-loop hero metrics (silent-failure share, PSV verified-success rate, funnel-stage regressions) and KEEP-slot baselines fromexecution-state.yaml+baselines.yaml. None of that exists in DOS — DOS is a domain-free trust substrate, not an apply pipeline; it has no runtime funnel, no hero metric, no baseline ledger. So the gate is re-grounded on the only "known-good" signals DOS actually has: a green kernel suite, a clean truth syscall, and a soak window. See "The gate" below.
Trunk is master. The stable tag is pinned on a commit reachable from
master; the push targets master's remote.
The kernel-vs-tooling boundary. The gate context script
(scripts/stable_release_context.py) and this skill are dev/release tooling
that operates ON the package — never imported BY dos.*. The
"kernel imports no host, no scripts/" litmus in CLAUDE.md stays intact.
Relationship to other systems
| System | Owns | Stable-release reads | Stable-release writes |
|---|---|---|---|
/release (scripts/release_bump.py) |
rolling vX.Y.Z tag, version markers |
the latest vX.Y.Z as promotion candidate |
nothing — never re-bumps |
the kernel suite (pytest) |
substrate correctness | exit code (green == eligible) | nothing |
the truth syscall (dos verify) |
ground-truth adjudication | exit + verdict (well-formed == eligible) | nothing |
| git tags | the channel itself | stable/* collision check + previous-stable |
one new stable/<codename> tag |
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.
- 5d ago First seen · 376 lines · 81 tokens per session scan A 800057bc5c0c
stable-release is a skill published in the GitHub repository anthony-chaudhary/dos-kernel (19 stars, last pushed 11d ago), licensed MIT. It adds 81 tokens to every session and 5,089 once invoked, about $0.0004 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
release-close-sprint
Use when the project owner wraps or closes a PuPu version/release — "关 0.1.10", "close the release", "版本收尾". Verifies a Size=Release parent issue and its direct sub-issues in GitHub Project, records close evidence there, and hands it to release certification.
release-open-sprint
Use when the project owner opens a new PuPu version/release — "开 0.1.11", "open the next release", "开新版本". Creates and scopes one Size=Release parent issue in PUPU Project; all version work is its direct sub-issues. Not for adding one item mid-release (release-draft-ticket) or closing a release (release-close-sprint).
b3os-release-ops
Skill "b3os-release-ops" from b3rys/b3rys-team-os, covering b3os-release-ops — 공개 배포·머지·핫픽스 게이트, 언제 invoke하나, 빠른 판정, 표준 실행 절차 and 1. pr merge 전.
org-pull-request
ワーカー完了報告に対するユーザー承認後の push / PR 作成 / CI 監視 / レビュー指摘ループ / PR マージ後の最終クローズを窓口が実行する。発動条件: (1) ワーカーから完了報告を受領しユーザーが「OK」「進めて」等の明示的承認を出した直後、 (2) GitHub PR にレビュー指摘 / CI 失敗が来てワーカーへ修正指示を送り直すとき、 (3) PR がマージされ最終クローズ条件を満たしたとき。 単に「ワーカーに作業を依頼する」初動は org-delegate であり本スキルではない。.
release
Use when writing a public-facing GitHub release announcement for a new version. Produces the curated short body users see on the releases page. Picks a shape that fits the release size (triplet for major, bullets for polish, single paragraph for hotfix). Separates the writer's surface from engineering's technical…
runtime-release-with-paired-ja-sync
Skill "runtime-release-with-paired-ja-sync" from suisya-systems/claude-org-ja, covering なぜこの skill が必要か, 発動条件, step 1: pre-fetch（リリース worker 派遣前）, step 2: リリース worker への impl-guidance and step 3: リリース land + tag push.