agentmods.dev

release-readiness

release-readiness is a skill for Claude Code, Codex from garagon/nanostack. It costs 45 tokens per session (1,119 once invoked), scanned A, original, Apache-2.0.

A release decision step that combines evidence already produced by review, quality assurance, security, licence, and privacy checks.

In plain words
What is it for?
Use it to resolve those five evidence sources, compose their results, and gate the /ship step.
Why use it?
It gives the delivery process one final status before shipping, based on the required upstream evidence.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the nanostack plugin — 18 skills, 1 command shipped together

not rated 204repo 2mo ago A scan SkillSpector: pass 45 tokens original Apache-2.0

Good fit Use it to resolve those five evidence sources, compose their results, and gate the /ship step.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/garagon/nanostack/release-readiness
View source ↗ garagon/nanostack nanostack.sh
Install

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.

Any agent
npx skills add garagon/nanostack --skill release-readiness
Clone the repo
git clone --depth 1 https://github.com/garagon/nanostack

Made for: Claude Code, Codex.

Or install nanostack, the plugin that ships this one along with the rest of its 18 skills, 1 command.

Wrote 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.

agentmods badge for release-readiness

README.md
[![agentmods](https://agentmods.dev/badge/skills/garagon/nanostack/release-readiness.svg)](https://agentmods.dev/skills/garagon/nanostack/release-readiness)
Your own site
<a href="https://agentmods.dev/skills/garagon/nanostack/release-readiness"><img src="https://agentmods.dev/badge/skills/garagon/nanostack/release-readiness.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,119 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.01119
Opus 5 $0.00023 $0.00560
Sonnet 5 $0.00009 $0.00224
Haiku 4.5 $0.00005 $0.00112

Measured 9d ago against content hash aebec5b9b07f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 9d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (bin/smoke.sh, bin/summarize.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

examples/custom-stack-template/compliance-release/skills/release-readiness/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/release-readiness — Release Decision Composer

You compose the sprint's release evidence into a single decision. You do not run any of the upstream skills; you read the artifacts they already saved and emit a status that gates /ship. The conductor's phase_graph puts you between the upstream phases and /ship, so this skill is the last thing that runs before delivery.

This is the release-readiness skill from the compliance-release stack. PR 2 of the Custom Stack Examples v1 round wires the real composer logic; this PR (PR 1) ships the skill structure so the static contract validates.

Process

0. Resolve paths (host-agnostic)

NANOSTACK_ROOT="${NANOSTACK_ROOT:-$HOME/.claude/skills/nanostack}"
SKILL_DIR="${SKILL_DIR:-$HOME/.claude/skills/release-readiness}"

1. Resolve upstream evidence

NANOSTACK_ROOT="${NANOSTACK_ROOT:-$HOME/.claude/skills/nanostack}"
"$NANOSTACK_ROOT/bin/resolve.sh" release-readiness

The resolver returns phase_kind: "custom" and upstream_artifacts with five keys: review, qa, security, license-audit, privacy-check. Each value is either a path to the artifact JSON or null if no artifact exists for that upstream.

2. Compose the decision

SKILL_DIR="${SKILL_DIR:-$HOME/.claude/skills/release-readiness}"
"$SKILL_DIR/bin/summarize.sh"

The helper reads each upstream artifact through bin/find-artifact.sh --verify and maps each to a check entry. Per-check status:

  • MISSING for any upstream whose artifact is absent.
  • TAMPERED for an artifact whose stored hash does not match the recomputed hash (evidence: "integrity_failure") or whose .integrity field is absent (evidence: "missing_integrity"). A release gate cannot trust evidence it cannot verify; an attacker who can modify the file can delete the field as easily as mutate the hash, so missing integrity is treated as the same risk class as a bad hash.
  • BLOCKED when the upstream's summary.status is BLOCKED.
  • WARN when the upstream's summary.status is WARN, or when no status is declared (artifact present but unannotated).
  • OK when the upstream's summary.status is OK and integrity verifies.

Read the full file on GitHub · 78 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 78 lines · 45 tokens per session scan A aebec5b9b07f

Subscribe to this mod's changes

release-readiness is a skill published in the GitHub repository garagon/nanostack (204 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,119 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.

Claude CodeGit and workflowReleasesai-agentsai-codingcodexdeveloper-tools
Related

Other skills, from other repositories

memstack-development-changelog-generator

Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.

cwinvestments/memstack · 63 tokens

ijfw-ship

Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…

FerroxLabs/ijfw · 139 tokens

ijfw-preflight

Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.

FerroxLabs/ijfw · 47 tokens

plate

Turn finished local work into a commit, an ordinary pull request, or a pull request stack. Use this skill to commit changes or to publish a branch. Use it to open or update a pull request. Use it to create, sync, restack, or submit a pull request stack. You can also run /plate. This skill owns all staging, commits…

paulnsorensen/easy-cheese · 106 tokens

plastic-releasing

Use when merging a feature branch to main and tagging a release, bumping the version, or when the user says "release", "tag", or "ship it".

zalom/plastic · 38 tokens

finishing-a-development-branch

Use when implementation is complete, tests pass, and you need to decide the integration path. Also use when asked to prepare a branch for release: 'update changelog', 'bump version', 'bump patch version', 'make sure changelog is correct', 'make sure version is correct'. Triggers: 'done with this branch', 'ready to…

axiomantic/spellbook · 134 tokens