agentmods.dev

deploy

deploy is a skill for Claude Code, Codex from xentivo/claude-plugins. It costs 98 tokens per session (1,247 once invoked), scanned A, original, MIT.

A deployment rule set for building and releasing an application through CI, the automated system that runs checks and deployment steps. It covers environment-specific workflows, release tags, concurrency, secrets, and verifying that the application actually starts.

In plain words
What is it for?
Use it when creating or changing deployment workflows, building release images, deploying versions, reloading secrets, or rolling back an application.
Why use it?
It prevents CI from drifting away from the repository's deployment process and from treating a successful API response as proof that the application is running.

Skill for Claude CodeCodex

Part of the pipeline plugin — 3 skills, 1 command shipped together

not rated 3 8d ago A scan 98 tokens original MIT
View the source file xentivo/claude-plugins
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.

agentmods
npx agentmods add skills/xentivo/claude-plugins/deploy
Any agent
npx skills add xentivo/claude-plugins --skill deploy
Clone the repo
git clone --depth 1 https://github.com/xentivo/claude-plugins

Made for: Claude Code, Codex.

Or install pipeline, the plugin that ships this one along with the rest of its 3 skills, 1 command.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/xentivo/claude-plugins/deploy.svg)](https://agentmods.dev/skills/xentivo/claude-plugins/deploy)
Your own site
<a href="https://agentmods.dev/skills/xentivo/claude-plugins/deploy"><img src="https://agentmods.dev/badge/skills/xentivo/claude-plugins/deploy.svg" alt="Measured on agentmods" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,247 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00098 $0.01247
Opus 5 $0.00049 $0.00624
Sonnet 5 $0.00020 $0.00249
Haiku 4.5 $0.00010 $0.00125

Measured 3d ago against content hash 7410c295f640, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deploy 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 3d 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.

plugins/pipeline/skills/deploy/SKILL.md · 73 lines

How it starts

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

Deploy z pipeline'u

Dwie rzeczy psują deploy w CI: druga implementacja tego, co robi się ręcznie, i uznanie odpowiedzi API za dowód, że aplikacja działa.

Pełna zasada organizacji: get_rule("ci-pipeline") na serwerze Xentivo MCP.

Kształt workflow

  • Osobny plik na środowisko. Nie jeden z parametrem: literówka w inputs albo w if celuje wtedy w produkcję. W nagłówku pliku napisz, gdzie jest bliźniak.
  • Workflow woła skrypt deployowy repo, tego samego, którego używa człowiek z laptopa. Kroki przepisane na YAML to druga implementacja, która rozjedzie się z pierwszą, a guardy skryptu (host bazy, czyste drzewo, walidacja schematu) przestaną chronić akurat tę ścieżkę, której nikt nie odpala ręcznie.
  • concurrency po środowisku z cancel-in-progress: false. Bieg zmienia stan.
  • workflow_dispatch zawsze, z inputem na ponowne wgranie sekretów i (dla produkcji) na tag do wdrożenia.
  • Produkcja jedzie z taga release'a, nie z czubka pnia. Pre-release nie jedzie i bramka kończy się zielono z wypisanym powodem.

Kroki, o których się zapomina

  • fetch-depth: 0, gdy numer buildu liczy się z historii gita.
  • Instalacja zależności, jeśli skrypt deployowy woła cokolwiek z npx przed buildem.
  • Odtworzenie .env z sekretu: umask 077, zero wypisywania zawartości, kontrola obecności kluczowej zmiennej i git status --porcelain (obraz powstaje z drzewa).
  • Sekrety aplikacji wgrywane tylko na jawne żądanie, nie przy każdym mergu.
  • Pominięcie builda przy zmianach, które nie wchodzą do obrazu: buduj, chyba że KAŻDA zmieniona ścieżka jest na liście wykluczeń. Diff z --no-renames, sprawdzenie wyniku poprzedniego biegu, powód wypisany zawsze.

Weryfikacja po deployu (kolejność jest częścią reguły)

  1. porównaj identyfikator obrazu przed i po - łapie „update nic nie podmienił",
  2. czekaj na stan Running, przerwij na Failed albo Degraded,
  3. dopiero teraz odpytuj health-check aż do 200 z oczekiwaną treścią.

Odwrócenie 2 i 3 przepuszcza zepsuty obraz: w trakcie rolloutu ruch idzie jeszcze na starą rewizję, która odpowiada 200. Przy porażce zrzuć ogon logów aplikacji (if: failure() + continue-on-error: true). W Summary daj rewizję, tag obrazu, adres i gotową komendę rollbacku.

Read the full file on GitHub · 73 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. 3d ago First seen · 73 lines · 98 tokens per session scan A 7410c295f640

Subscribe to this mod's changes

deploy is a skill published in the GitHub repository xentivo/claude-plugins (3 stars, last pushed 8d ago), licensed MIT. It adds 98 tokens to every session and 1,247 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.

CI and CDCloudDevOps and cloud
Related

Other skills, from other repositories

use-vercel-action

Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI. Use when the user asks to deploy to Vercel from GitHub Actions, add Vercel preview deploys, post a Vercel preview URL on a PR, configure prebuilt Vercel deployments, set up alias domains for previews, create a GitHub…

amondnet/vercel-action · 151 tokens

create-install-scripts

Generate CI/CD installation scripts for AWS CDK projects. Use when setting up deployment pipelines, creating install.sh scripts, configuring GitLab CI, or setting up AWS CodeBuild for CDK deployments.

aws-samples/sample-agent-skills-for-builders · 44 tokens

deployment

Deploy applications to DigitalOcean App Platform via GitHub Actions with proper environment management and secrets handling. Use when setting up CI/CD pipelines, configuring staging/production environments, managing deployment secrets, or creating GitHub Actions workflows.

digitalocean-labs/do-app-platform-skills · 46 tokens

setup

Use when bootstrapping a Rails project: context, onboarding, CI. Trigger words: setup project, rails new, CI/CD, dev environment, Gemfile.

igmarin/rails-agent-skills · 35 tokens

ship-issue

One-command issue-to-merge pipeline orchestrator. Drives a GitHub issue through nine stages (preflight, plan, implement, review, ci, cloudreview, deploy, e2e, logs) with two human gates, persisting all run state to files so a crashed or interrupted run resumes losslessly. Triggers on "/ship-issue" with an issue number…

mhylle/claude-skills-collection · 88 tokens

aws-codepipeline-and-codedeploy

Designs AWS CodePipeline stage/action structure and integrates it with CodeDeploy deployment groups and appspec.yml for EC2/on-prem, ECS, or Lambda deploys. Use when the user asks to "set up CodePipeline," "add a CodeDeploy deployment group," "write an appspec.yml," "wire CodePipeline to CodeDeploy," "troubleshoot a…

selvarajmurugesan90/ops-engineering-skills · 101 tokens