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 sidiangongyuan/codex-skills-library --skill app-release-readinessgit clone --depth 1 https://github.com/sidiangongyuan/codex-skills-libraryWrote 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/sidiangongyuan/codex-skills-library/app-release-readiness)<a href="https://agentmods.dev/skills/sidiangongyuan/codex-skills-library/app-release-readiness"><img src="https://agentmods.dev/badge/skills/sidiangongyuan/codex-skills-library/app-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/sidiangongyuan/codex-skills-library/app-release-readiness"><img src="https://agentmods.dev/badge/skills/sidiangongyuan/codex-skills-library/app-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.00049 | $0.00804 |
| Opus 5.5 | $0.00020 | $0.00322 |
| Sonnet 5.5 | $0.00010 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
app-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 1mo 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Release Readiness
Use this skill when a user asks to submit, push, package, upload an installer, or confirm that the latest app update is actually available.
Workflow
-
Preflight the repository.
- Run
git status --shortand identify unrelated changes. - Confirm branch, remote, version/tag policy, and whether this is a source commit, installer upload, or both.
- Do not commit build artifacts unless the repo explicitly tracks them.
- If the user asks to limit old GitHub Releases for a maintained desktop app and gives no other number, keep the newest 15 release records and do not delete git tags.
- Run
-
Verify before packaging.
- Run the smallest meaningful backend/frontend tests for the change.
- Run full build checks when UI, packaging, provider, or app lifecycle code changed.
- For desktop apps, include Rust/Tauri or native shell checks when present.
- Scan for key-shaped secrets and private data when provider credentials, release notes, screenshots, or docs changed.
-
Package with process safety.
- Close or handle app/sidecar processes before overwriting binaries.
- Prefer installers that fail on locked files over half-updated installs.
- Ensure uninstall/update behavior does not delete user data by default.
-
Inspect build outputs.
- Record installer paths, sizes, and SHA256 hashes.
- Compare expected sidecar/app binaries when stale-process or half-update bugs were part of the release.
- Smoke-test the installed app when feasible.
-
Commit and push deliberately.
- Stage only intended source/docs changes.
- Use a direct commit message that names the user-visible change.
- Push the branch and verify the remote commit SHA before publishing source claims or release notes that point at the new version.
-
Upload release assets when requested.
- Use the repository's current release/tag policy.
- Upload with replace/clobber only when the user asked for the latest asset to replace the old one.
- Verify remote asset names and sizes after upload.
- Download uploaded assets back from the release URL and verify SHA256 against the local artifacts before saying the release is current.
What ships with it
4 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.
- 1mo ago First seen · 86 lines · 49 tokens per session scan A c9ccc70d12a9
app-release-readiness is a skill published in the GitHub repository sidiangongyuan/codex-skills-library (24 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 804 once invoked, about $0.0002 per session on Opus 5.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.
aiwg-pr
AIWG-specific pull request delivery workflow for AIWG product/workspace changes; not the generic repository PR process.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
git-mirror-audit
Verify configured secondary git mirrors are present and not drifting from the primary remote/default branch.
aiwg-delivery-pr
AIWG-specific delivery pull request workflow; explicit alias for aiwg-pr, not a generic repository PR guide.
git-workflow
A Git workflow guide for organizing commits, branches, pull requests, releases, and automated version-control tasks. Git is the system developers use to track code changes and collaborate.