Borrowing it
Nothing to install: this file belongs to haojing8312/WorkClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/haojing8312/WorkClaw/main/.agents/skills/workclaw-release-readiness/SKILL.mdgit clone --depth 1 https://github.com/haojing8312/WorkClawWrote 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/haojing8312/workclaw/workclaw-release-readiness)<a href="https://agentmods.dev/skills/haojing8312/workclaw/workclaw-release-readiness"><img src="https://agentmods.dev/badge/skills/haojing8312/workclaw/workclaw-release-readiness/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/haojing8312/workclaw/workclaw-release-readiness"><img src="https://agentmods.dev/badge/skills/haojing8312/workclaw/workclaw-release-readiness.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.00463 |
| Opus 5 | $0.00020 | $0.00231 |
| Sonnet 5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
workclaw-release-readiness 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WorkClaw Release Readiness
Overview
Use this skill for shipping-sensitive changes. It separates release readiness from ordinary code verification and produces a clear ship recommendation with evidence.
When to Use
- Version files or release metadata changed
- Installer branding or installer checks changed
- Release docs changed
- Packaging outputs or desktop build expectations changed
- Vendor lane or upstream sync release paths changed
- A branch is being assessed for ship readiness after release-sensitive work
Do not use this for ordinary feature work that does not touch release-sensitive surfaces.
Command Routing
- Run
pnpm release:check-versionfor version and release metadata changes. - Run
pnpm test:releasefor release-path validation. - Run
pnpm test:installerfor installer branding or installer flow changes. - Run
pnpm test:release-docsfor release note or release document changes. - Run
pnpm test:openclaw-vendor-lanefor vendor sync or lane changes. - Run
pnpm build:runtimewhen packaging output or desktop build behavior changed.
Required Output
- Release verdict:
GREEN,YELLOW, orRED - Blocking issues, if any
- Required release-note or documentation follow-ups
- Final recommendation on whether the branch is safe to ship
Output Template
Use this shape:
## Release Readiness
- Verdict: GREEN | YELLOW | RED
- Changed release surface:
- Commands run:
- Blocking issues:
- Required follow-ups:
- Ship recommendation:
Core Pattern
- Identify which release-sensitive surface changed.
- Run the matching release commands.
- Start from "safe to ship" and only downgrade when there is concrete evidence.
- If blocked, provide an explicit unblock checklist.
Common Mistakes
- Treating release-doc or installer changes as low-risk and skipping dedicated checks.
- Reporting a release verdict without citing commands or evidence.
- Mixing ordinary runtime verification with ship-readiness judgment and losing the release signal.
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.
- 9d ago First seen · 58 lines · 40 tokens per session scan A cc398c23ea67
workclaw-release-readiness is a skill published in the GitHub repository haojing8312/WorkClaw (140 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 463 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.