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.
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 agentmods add commands/aws/agent-toolkit-for-aws/release-readinessgit clone --depth 1 https://github.com/aws/agent-toolkit-for-awsWrote 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/commands/aws/agent-toolkit-for-aws/release-readiness)<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="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 | $0.00021 | $0.01930 |
| Opus 5 | $0.00010 | $0.00965 |
| Sonnet 5 | $0.00004 | $0.00386 |
| Haiku 4.5 | $0.00002 | $0.00193 |
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 5d 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 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_reviewaws_devops_agent__get_taskaws_devops_agent__list_journal_recordsaws_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-agentskill 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
$ARGUMENTScontains 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
$ARGUMENTSis a repo name or path, use the "Local GitHub/GitLab repo" flow below. - If
$ARGUMENTSis empty, check the current git repository and use the local flow. - Build the
contentobject 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: callaws_devops_agent__get_release_readiness_report(execution_id=EXEC_ID), save to file, and run the auto-fix flow from the skill.
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.
- 5d ago First seen · 173 lines · 21 tokens per session scan A 4bd6c608b90b
release-readiness is a command published in the GitHub repository aws/agent-toolkit-for-aws (2,518 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 1,930 once invoked, about $0.0001 per session on Opus 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.
Other commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
Prepare a release by updating docs and bumping the version.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.