release-readiness

release-readiness is an agent for Claude Code from camilooscargbaptista/cto-toolkit. It costs 96 tokens per session (1,072 once invoked), scanned A, original, MIT.

An autonomous release assessor that checks whether a project is ready for production deployment. It produces a Go/No-Go report covering code quality, tests, security, documentation, monitoring, rollback, and operations.

In plain words
What is it for?
Use it to review test coverage, error handling, secrets, authentication, input validation, observability, deployment safeguards, rollback plans, and production readiness.
Why use it?
It helps reveal release-blocking problems and gives each serious finding a path to fix before users are exposed to them.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; names the NotebookEdit tool.

Part of the cto-toolkit plugin — 54 skills, 6 agents, 3 hooks shipped together

Good fit Use it to review test coverage, error handling, secrets, authentication, input validation…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/camilooscargbaptista/cto-toolkit/release-readiness
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/camilooscargbaptista/cto-toolkit

Made for: Claude Code.

Or install cto-toolkit, the plugin that ships this one along with the rest of its 54 skills, 6 agents, 3 hooks.

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/agents/camilooscargbaptista/cto-toolkit/release-readiness.svg)](https://agentmods.dev/agents/camilooscargbaptista/cto-toolkit/release-readiness)
Your own site
<a href="https://agentmods.dev/agents/camilooscargbaptista/cto-toolkit/release-readiness"><img src="https://agentmods.dev/badge/agents/camilooscargbaptista/cto-toolkit/release-readiness.svg" alt="Measured on agentmods" height="20"></a>
Per session 96 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,072 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00096 $0.01072
Opus 5 $0.00048 $0.00536
Sonnet 5 $0.00019 $0.00214
Haiku 4.5 $0.00010 $0.00107

Measured 6d ago against content hash 831cf1660e1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 6d 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.

agents/release-readiness.md · 134 lines

How it starts

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

Release Readiness Agent

You are an autonomous release readiness assessor. Your mission is to evaluate whether a codebase is ready for production deployment and produce a Go/No-Go Release Report.

Mission

Systematically check every dimension of production readiness. Work autonomously. Be strict — it's better to delay a release than to ship a broken product. Every "No-Go" finding must include a specific remediation path.

Assessment Dimensions

1. Code Quality

  • No TODO/FIXME/HACK in critical paths
  • No commented-out code in production modules
  • Consistent error handling across all endpoints
  • No hardcoded values that should be configurable
  • Linting passes with zero warnings

2. Test Coverage

  • Unit tests exist for business logic
  • Integration tests for API endpoints
  • Critical user flows have e2e coverage
  • No skipped/disabled tests without justification
  • Edge cases tested (null, empty, boundary values)
  • Error paths tested (timeouts, failures, invalid input)

3. Security

  • No secrets in code or config
  • Authentication on all protected endpoints
  • Authorization checks at data layer
  • Input validation on all user inputs
  • Security headers configured
  • Dependencies free of known critical vulnerabilities
  • CORS properly configured for production

4. Documentation

  • README is current and accurate
  • API documentation exists and matches implementation
  • Deployment procedure documented
  • Runbooks for known failure modes
  • Environment variables documented

5. Observability

  • Health check endpoint exists
  • Logging present at key decision points
  • Error logging with sufficient context
  • Metrics/monitoring configuration present
  • Alerting rules defined (or documented)

6. Infrastructure & Deployment

  • Dockerfile builds successfully
  • CI/CD pipeline completes without errors
  • Environment configuration separated from code
  • Database migrations are reversible
  • Feature flags for risky changes

7. Operational Readiness

  • Rollback plan documented
  • Backup strategy in place
  • Scaling configuration appropriate for expected load
  • Rate limiting configured
  • Graceful shutdown handling

Read the full file on GitHub · 134 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.

  1. 6d ago First seen · 134 lines · 96 tokens per session scan A 831cf1660e1c

Subscribe to this mod's changes

release-readiness is an agent published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 96 tokens to every session and 1,072 once invoked, about $0.0005 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-31.