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 skills add Kin9Zeus/senior-engineer-skills --skill release-readinessgit clone --depth 1 https://github.com/Kin9Zeus/senior-engineer-skillsWrote 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/kin9zeus/senior-engineer-skills/release-readiness)<a href="https://agentmods.dev/skills/kin9zeus/senior-engineer-skills/release-readiness"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/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/kin9zeus/senior-engineer-skills/release-readiness"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/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.00124 | $0.02292 |
| Opus 5 | $0.00062 | $0.01146 |
| Sonnet 5 | $0.00025 | $0.00458 |
| Haiku 4.5 | $0.00012 | $0.00229 |
Grade A, and why
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 11d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness
The purpose of a gate is to make a decision explicit rather than implicit. Shipping with known gaps is legitimate — shipping without knowing what they are is not.
Produce one of three verdicts, in writing:
GO No blockers. Ship.
GO WITH RISK Named, accepted, owned risks. Ship, with mitigations listed.
NO GO Named blockers. Do not ship until these close.
Never soften a NO GO into "mostly ready". If a blocker is real, say so in the
first line and name it.
The blockers — any one of these is NO GO
These are not judgement calls. Each one causes a breach, data loss, or a legal exposure that the launch cannot be undone from.
- A secret is in the repository or its git history. Rotate first, then purge.
- Any user can access another user's data. Test it: authenticate as A, request B's resource.
- No backups, or backups that have never been restored.
- Personal data is processed with no privacy policy, or a policy that omits a processor actually receiving data.
- No way to delete user data when the policy or the law says there is.
- Payments where amounts are computed or trusted from the client.
- A webhook that mutates state without verifying its signature.
- String-interpolated SQL on a route reachable by a user.
- Debug mode enabled, or stack traces returned to clients.
- No rollback path that anyone has ever executed.
- A migration with no tested reverse running against production data.
- A known critical vulnerability in a reachable dependency.
If any box is unticked, the verdict is NO GO and the report is short.
The gate
1 · Security
- Secret scan clean, including git history
- Object-level authorization tested — the cross-user test exists and passes
- Authentication: hashing, session invalidation, rate limits, no user enumeration
- Input validated by schema at every entry point, including webhooks and queue consumers
- Security headers set; CSP without
unsafe-inline - Dependency audit run, output read, high-severity issues resolved or accepted in writing
- Debug off; stack traces not returned; admin surfaces network-restricted
- Rate limiting on auth and all mutations
- Uploads: type verified by content, size capped, served from a separate origin
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 233 lines · 124 tokens per session scan A faa2fbb92942
release-readiness is a skill published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 17d ago), licensed MIT. It adds 124 tokens to every session and 2,292 once invoked, about $0.0006 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-31.
Other skills, from other repositories
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
version-release
Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.