What is release-readiness?

A pre-merge review command for a change waiting to be added to a code project. It can review a GitHub pull request, GitLab merge request, or local branch for release readiness.

It helps assess whether a pull request, merge request, or branch is ready to merge and release, using the supplied repository and change details.

It gives teams a structured check before merging code, helping identify issues that could delay or complicate a release.

release-readiness — Command for Claude Code by aws

About the project

Agent Toolkit for AWS is a collection of AWS-supported MCP servers, skills, plugins, commands, and hooks that help AI coding agents build, deploy, and manage applications on AWS. It is used by developers working with AWS services through agents such as Claude Code, Codex, Cursor, and Kiro. The catalogue entries are the toolkit's own agent extensions for AWS development and operations.

aws/agent-toolkit-for-aws · 2,919 stars · on GitHub

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.

Clone the repo

git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws

Made for: Claude Code.

Or install aws-agents-for-devsecops, the plugin that ships this one along with the rest of its 13 skills, 9 commands, 1 MCP server.

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/commands/aws/agent-toolkit-for-aws/release-readiness/github.svg)](https://agentmods.dev/commands/aws/agent-toolkit-for-aws/release-readiness)

Your own site

<a href="https://agentmods.dev/commands/aws/agent-toolkit-for-aws/release-readiness"><img src="https://agentmods.dev/badge/commands/aws/agent-toolkit-for-aws/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/aws/agent-toolkit-for-aws/release-readiness"><img src="https://agentmods.dev/badge/commands/aws/agent-toolkit-for-aws/release-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,930 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.00021	$0.01930
Opus 5.5	$0.00008	$0.00772
Sonnet 5.5	$0.00004	$0.00386
Haiku 4.5	$0.00002	$0.00193

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

Security

Grade A, and why

release-readiness scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**IMPORTANT: NEVER use `gh` CLI, `glab` CLI, `curl`, or any external tool to fetch PR/MR details. All required fields (repository, prNumber/mergeRequestIid, hostname) MUST be parsed directly from the URL string. The DevO

plugins/aws-agents-for-devsecops/commands/release-readiness.md · 173 lines

How it starts

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

Read and follow the analyzing-release-readiness skill for full execution details.

IMPORTANT: NEVER use gh CLI, glab CLI, curl, or any external tool to fetch PR/MR details. All required fields (repository, prNumber/mergeRequestIid, hostname) MUST be parsed directly from the URL string. The DevOps Agent fetches the content itself.

Step 0 — Choose your execution path (DO THIS FIRST)

Check your available tools. Do you have ALL of these tools?

aws_devops_agent__create_release_readiness_review
aws_devops_agent__get_task
aws_devops_agent__list_journal_records
aws_devops_agent__get_release_readiness_report

These tools are NOT deferred/lazy-loaded — if they do not appear in your tool list, they are unavailable. Do NOT search for them via ToolSearch.

YES (all present) → Use the "Remote Server" path below
NO → Tell the user: "Remote server not configured." Then prompt the user with instructions from the setup-devops-agent skill if they intend to set up the connection. If not, mention that you are "proceeding with the AWS CLI fallback." Then use the Fallback (CLI) path below.

Common to both paths (see skill: "Gathering execution parameters")

If $ARGUMENTS contains a URL (github.com or gitlab.com), parse the PR/MR details directly from the URL string — do NOT fetch or inspect the PR via any tool.
If $ARGUMENTS is a repo name or path, use the "Local GitHub/GitLab repo" flow below.
If $ARGUMENTS is empty, check the current git repository and use the local flow.
Build the content object following the skill's "Gathering execution parameters" section.
Ask the user about automated testing (static-only vs full analysis). Do NOT proceed until the user answers.

Remote Server path (see skill: "Core workflow")

Call aws_devops_agent__create_release_readiness_review(content={...}, skip_automated_testing=...).
Poll aws_devops_agent__get_task(task_id=TASK_ID) every 30s.
Stream progress via aws_devops_agent__list_journal_records(execution_id=EXEC_ID, order="ASC").
On COMPLETED: call aws_devops_agent__get_release_readiness_report(execution_id=EXEC_ID), save to file, and run the auto-fix flow from the skill.

Read the full file on GitHub · 173 lines

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.

1mo ago First seen · 173 lines · 21 tokens per session scan A 4bd6c608b90b

Subscribe to this mod's changes

release-readiness is a command published in the GitHub repository aws/agent-toolkit-for-aws (2,919 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 1,930 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Git and workflow Releases

release-readiness

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

Step 0 — Choose your execution path (DO THIS FIRST)

Common to both paths (see skill: "Gathering execution parameters")

Remote Server path (see skill: "Core workflow")

What this file has done since we first saw it

Other commands, from other repositories

release

ia-document-release

ia-changelog

release

release-tag

release