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 cherninlab/ennodia --skill release-readinessgit clone --depth 1 https://github.com/cherninlab/ennodiaWrote 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/cherninlab/ennodia/release-readiness)<a href="https://agentmods.dev/skills/cherninlab/ennodia/release-readiness"><img src="https://agentmods.dev/badge/skills/cherninlab/ennodia/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/cherninlab/ennodia/release-readiness"><img src="https://agentmods.dev/badge/skills/cherninlab/ennodia/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.00026 | $0.00127 |
| Opus 5.5 | $0.00010 | $0.00051 |
| Sonnet 5.5 | $0.00005 | $0.00025 |
| Haiku 4.5 | $0.00003 | $0.00013 |
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 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.
What it actually says
Release Readiness
Assess the work as if it will ship in a public release candidate.
Check:
- install and package behavior
- public docs and examples
- CLI or MCP API compatibility
- quality gates and verification commands
- failure modes and recovery paths
- whether the release note would be honest and understandable
Prefer small, shippable fixes over broad rewrites. Call out any issue that would make first-time users distrust the tool.
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 · 20 lines · 26 tokens per session scan A 6d5b7209ec9a
release-readiness is a skill published in the GitHub repository cherninlab/ennodia (6 stars, last pushed 29d ago), licensed MIT. It adds 26 tokens to every session and 127 once invoked, about $0.0001 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
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
ship
Ship phase. Runs isolated integration test in a fresh worktree, creates a PR with full spec + audit report in the body, watches CI, and auto-fixes failures.
release-pr-quality-gate
Build an AgentWorks release or pull-request browser quality gate over saved suites and exact build identity. Use when a merge, deployment, or promotion needs an auditable QA decision.
matilha-gather
Use when completed subprojects are ready to merge — validates SP-DONE.md strict gates, merges --no-ff in mergeorder, runs per-SP regression, updates wave-NN-status.md.
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.