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 jh941213/codex-lattice --skill release-readinessgit clone --depth 1 https://github.com/jh941213/codex-latticeWrote 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/jh941213/codex-lattice/release-readiness)<a href="https://agentmods.dev/skills/jh941213/codex-lattice/release-readiness"><img src="https://agentmods.dev/badge/skills/jh941213/codex-lattice/release-readiness.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.00049 | $0.00361 |
| Opus 5 | $0.00024 | $0.00180 |
| Sonnet 5 | $0.00010 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
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 8d 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 Readiness
Use this skill before PR, merge, deploy, version bump, or production handoff.
Workflow
- Identify release scope from
git diff,docs/harness/TASKS.md, anddocs/harness/CHANGELOG.md. - Confirm the release has clear acceptance criteria in
docs/harness/FEATURE_SPEC.md. - Verify evidence exists in
docs/harness/VALIDATION.md. - Check rollback and backout notes in
docs/harness/RELEASE_PLAN.md. - Check migration risk in
docs/harness/MIGRATION_PLAN.md. - Check operator impact in
docs/harness/OPERATIONS_RUNBOOK.md. - Check security and data impact in
docs/harness/SECURITY_POLICY.mdanddocs/harness/DATA_GOVERNANCE.mdwhen present. - Update
docs/harness/RISKS.mdwith unresolved release blockers.
Required Output
Return:
- release scope
- validation evidence
- rollback path
- migration/data impact
- operator notes
- blockers
- release decision:
READY,READY_WITH_RISK, orBLOCKED
Blockers
Treat these as release blockers unless the user explicitly accepts the risk:
- no verification evidence for changed behavior
- no rollback path for stateful changes
- unreviewed auth, permissions, secrets, or PII changes
- migrations without compatibility or rollback notes
- production-facing changes without operator notes
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.
- 8d ago First seen · 42 lines · 49 tokens per session scan A 7630eaecf12f
release-readiness is a skill published in the GitHub repository jh941213/codex-lattice (19 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 361 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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.