deploy-release

deploy-release is a skill for Codex from HoangNguyen0403/agent-skills-standard. It costs 17 tokens per session (967 once invoked), scanned A, original, MIT.

A deployment workflow for preparing and checking a staged or production release, including smoke checks and a rollback plan.

In plain words
What is it for?
Use it to confirm approvals and configuration, deploy to staging, run basic health checks, promote the release, and monitor logs, metrics, errors, and latency.
Why use it?
It reduces the risk of shipping an unready change and provides a defined way to recover when deployment checks or user flows fail.

Skill for Codex

Written for Codex: installed under .codex/.

Good fit Use it to confirm approvals and configuration, deploy to staging, run basic health checks, promote the release, and monitor logs, metrics, errors, and latency.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hoangnguyen0403/agent-skills-standard/deploy-release
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 HoangNguyen0403/agent-skills-standard --skill deploy-release
Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: 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.

agentmods badge for deploy-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/deploy-release/github.svg)](https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/deploy-release)
Your own site
<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/deploy-release"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/deploy-release/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.

agentmods 80×15 button for deploy-release

Your own site · 80×15
<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/deploy-release"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/deploy-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 967 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.00017 $0.00967
Opus 5.5 $0.00007 $0.00387
Sonnet 5.5 $0.00003 $0.00193
Haiku 4.5 $0.00002 $0.00097

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

Security

Grade A, and why

deploy-release 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 12d 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.

.codex/skills/deploy-release/SKILL.md · 93 lines

How it starts

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

Deploy Release Skill

[!IMPORTANT] Prepare and verify a staged or production deployment with rollback and smoke checks.

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

Deploy Release Workflow

Goal: Ship verified work with explicit deployment steps, smoke checks, and rollback criteria.

Steps

  1. Confirm readiness:
    • Verification report is PASS or accepted with documented risk.
    • Required approvals are present, and production carries a named release owner's authorization; proposal in ledger is not execution or release permission.
    • Migrations, feature flags, and measurement contracts are accounted for. When initiative uses product evidence (docs/product/<slug>/evidence.json), carry measurement owner, registered MET baseline OR exact scoped exception DEC, query, instrumentation, cohort, window, guardrails, and review trigger; never fabricate agent-created baselines, approval, or causal ROI.
    • release_confidence is high, or medium with documented risk; low means NO-GO unless the release owner overrides in writing.
  2. Prepare release:
    • Identify version, environment, deploy command, and owner.
    • Confirm secrets, config, queues, cron, and external services.
    • Define rollback command or revert path.
    • Environment tier: dev deploys freely; staging deploys behind the smoke gate; production is prepared by the agent and authorized by the named release owner through the guardrail approval gate.
  3. Deploy:
    • Run staging deploy first when available.
    • Rehearse the rollback in staging before promoting to production.
    • Run smoke checks before promotion.
    • Promote only when smoke checks pass.
  4. Monitor:
    • Check logs, metrics, errors, latency, and core user flows.
    • Guardrail harm or regression escalates immediately to authorized incident controls (incident-hotfix); stop or roll back on defined failure signals.
  5. Persist and route:
    • Write run record to artifacts/runs/[slug]/[compactISO]-deploy-release.json when file writes allowed. Feature feature_status=released is preserved even when product value observations remain pending or inconclusive.
    • User-facing notes -> publish-notes.
    • Process and standards feedback -> retro-learn.

Read the full file on GitHub · 93 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. 12d ago Changed · -1 lines 64951fce2fa7
  2. 28d ago Changed · +1 lines d9c3d09cc523
  3. 1mo ago Changed · +1 lines 567d4a8d9ab3
  4. 1mo ago Changed · +1 lines e78cffc88048
  5. 1mo ago First seen · 91 lines · 17 tokens per session scan A 4b113c18eaee

Subscribe to this mod's changes

deploy-release is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 967 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

adapter-aws-lambda

Deploy tRPC on AWS Lambda with awsLambdaRequestHandler() from @trpc/server/adapters/aws-lambda for API Gateway v1 (REST, APIGatewayProxyEvent) and v2 (HTTP, APIGatewayProxyEventV2), and Lambda Function URLs. Enable response streaming with awsLambdaStreamingRequestHandler() wrapped in awslambda.streamifyResponse().…

trpc/trpc · 93 tokens

adapter-fetch

Deploy tRPC on WinterCG-compliant edge runtimes with fetchRequestHandler() from @trpc/server/adapters/fetch. Supports Cloudflare Workers, Deno Deploy, Vercel Edge Runtime, Astro, Remix, SolidStart. FetchCreateContextFnOptions provides req (Request) and resHeaders (Headers) for context creation. The endpoint option…

trpc/trpc · 86 tokens

nextjs-idioms

Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.

irahardianto/awesome-agv · 55 tokens

react-idioms

React 19+ patterns: custom hooks, Suspense boundaries, state management, component composition, and web performance. Use when developing or refactoring React components and client applications. Pair with typescript-idioms.

irahardianto/awesome-agv · 48 tokens

vercel-microfrontends

Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json…

vercel/microfrontends · 122 tokens

oma-tf-infra

Create or review Terraform infrastructure and plans. Use for cloud resources, IAM, networking, state management, and infrastructure changes.

first-fluke/fullstack-starter · 30 tokens