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/lglucas/ai-dev-operating-system/release-checknpx skills add lglucas/ai-dev-operating-system --skill release-checkgit clone --depth 1 https://github.com/lglucas/ai-dev-operating-systemWrote 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/lglucas/ai-dev-operating-system/release-check)<a href="https://agentmods.dev/skills/lglucas/ai-dev-operating-system/release-check"><img src="https://agentmods.dev/badge/skills/lglucas/ai-dev-operating-system/release-check.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.1 | $0.00098 | $0.00434 |
| Opus 5 | $0.00049 | $0.00217 |
| Sonnet 5 | $0.00020 | $0.00087 |
| Haiku 4.5 | $0.00010 | $0.00043 |
Grade A, and why
release-check 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 6d 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.
What it actually says
Release Check
Required checks
Do not re-implement checks that already have a skill. Delegate, then record the verdict.
| Check | Delegate to | Blocking? |
|---|---|---|
| Tests pass | project test runner | yes |
| Build + dev server + main flow load | verify-build-works |
yes |
| No leaked secrets or credentials | secrets-scan |
yes |
| Personal-data changes reviewed | privacy-audit |
yes, when applicable |
| Changelog updated | — | yes |
| Codemap em dia | codemap — node scripts/codemap.js --check |
yes |
| Sprint doc updated | sprint-management |
yes |
| Session logs or ADRs for important decisions | decision-log |
warning |
| OS structure still coherent | os-self-test |
warning |
| Coordinator review complete | coordinator-agent |
yes |
For a hard-to-reverse release decision (first public launch, pricing change shipping with the release, irreversible migration), run multi-ai-review before issuing a verdict.
Output
Release candidate:
Blocking issues:
Warnings:
Verdict: RELEASE | RELEASE_WITH_NOTES | BLOCK
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.
- 6d ago First seen · 35 lines · 98 tokens per session scan A 689db858661a
release-check is a skill published in the GitHub repository lglucas/ai-dev-operating-system (11 stars, last pushed 27d ago), licensed MIT. It adds 98 tokens to every session and 434 once invoked, about $0.0005 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
Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.
changelog-generation
Changelog generation skill for ZeroClaw releases. Use this skill when the user wants to generate a changelog, prepare release notes, or summarize what changed between versions. Trigger on: 'generate changelog', 'changelog for v0.7.x', 'prepare release notes', 'what changed since ', 'write the changelog'…
herdr-pre-release-audit
Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's pre-release audit, validate docs/next before release, inspect issue refs that release CI will close, or finalize release docs for herdr.
release-notes
Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with "Verbed + Impact + Scenario" style…
release
Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version.
release-preview
Cut an AgentOS release-preview. Use when the user asks for a preview, release-preview, or a branch dist-tag build.