What is release-plan?

A release declaration and rollout decision tool for one change. It records the versioned artifact, rollout stages, health and business limits, rollback action, and outcome metric, then decides whether each stage should proceed, pause, or roll back.

Use it to prepare release.md, validate it against planning records, and drive promote, hold, or rollback decisions during staged deployment.

It replaces informal release decisions with thresholds written before deployment. This gives the rollout process a defined response when health or business results are outside the limits.

release-plan — Skill for Claude Code and Codex by ALTEN-group

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 ALTEN-group/coding-pal --skill release-plan

Clone the repo

git clone --depth 1 https://github.com/ALTEN-group/coding-pal

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alten-group/coding-pal/release-plan/github.svg)](https://agentmods.dev/skills/alten-group/coding-pal/release-plan)

Your own site

<a href="https://agentmods.dev/skills/alten-group/coding-pal/release-plan"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/release-plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alten-group/coding-pal/release-plan"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/release-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 803 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00093	$0.00803
Opus 5.5	$0.00037	$0.00321
Sonnet 5.5	$0.00019	$0.00161
Haiku 4.5	$0.00009	$0.00080

Measured 4d ago against content hash b6a792002ab4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-plan 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 4d ago.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/evaluate-rollout.mjs, scripts/evaluate-rollout.test.mjs, scripts/release-fixture.mjs, …), 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.

skills/release-plan/SKILL.md · 53 lines

How it starts

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

Release Plan

Produce deterministic release.md declarations that DevOps can approve quickly and the rollout pipeline can execute without judgement calls. AI drafts and proposes thresholds; DevOps decides. Promotion and rollback are computed by a script against thresholds declared before deployment.

When to Use This Skill

A merged change must be declared for release: tier, artifact, flag, rollout stages, thresholds, rollback, and outcome metric.
CI must gate a release tag by validating release.md against think.md and plan.md.
A rollout pipeline must decide, for one stage, whether to promote, hold, or roll back.

Path resolution

Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/release-plan/ or .claude/skills/release-plan/, use that base path.

Workflow

Read references/release-contract.md now. It is the authoritative source for headings, fields, stage shapes per tier, threshold rules, and rollback mechanisms.
Draft release.md from think.md (tier and rollback), plan.md (raised tier, file scope), and the Triage hypothesis (outcome metric). Propose thresholds from the tier defaults in the contract. Never invent a baseline: take it from the Triage evidence or leave a question.
Validate with the deterministic script from this skill's directory:

node scripts/validate-release.mjs --release specs/issue-42/release.md \
  --think specs/issue-42/think.md --plan specs/issue-42/plan.md

# Or the whole work item directory, plus the git tag in CI
node scripts/validate-release.mjs --dir specs/issue-42 --tag v1.4.0

Treat a nonzero validator exit as invalid output and fix the file rather than ignoring errors. Model compliance is advisory; the script is the enforcement gate.

In the rollout pipeline, decide each stage with no AI:

node scripts/evaluate-rollout.mjs --release specs/issue-42/release.md --stage canary-5 --metrics metrics.json

Read the full file on GitHub · 53 lines

Files

What ships with it

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

4d ago First seen · 53 lines · 93 tokens per session scan A b6a792002ab4

Subscribe to this mod's changes

release-plan is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 93 tokens to every session and 803 once invoked, about $0.0004 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-10-14.

Cloud DevOps and cloud Git and workflow Releases

release-plan

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Release Plan

When to Use This Skill

Path resolution

Workflow

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

land-and-deploy

publish-site

release-publish

release-review

orchard-release

orchard-review