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.

Use it when creating or changing deployment workflows, building release images, deploying versions, reloading secrets, or rolling back an application.

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.

deploy — Skill for Claude Code by 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.

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.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/xentivo/claude-plugins/deploy/github.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/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/skills/xentivo/claude-plugins/deploy"><img src="https://agentmods.dev/badge/skills/xentivo/claude-plugins/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 129 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,057 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.

Model	Per session	Once invoked
Fable 5.1	$0.00129	$0.02057
Opus 5.5	$0.00052	$0.00823
Sonnet 5.5	$0.00026	$0.00411
Haiku 4.5	$0.00013	$0.00206

Measured 1mo ago against content hash 9fbceebcfd21, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

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 · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 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)

porównaj identyfikator obrazu przed i po - łapie „update nic nie podmienił",
czekaj na stan Running, przerwij na Failed albo Degraded,
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 · 118 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 Changed · +45 lines · +31 tokens per session 9fbceebcfd21
1mo 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 (4 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 2,057 once invoked, about $0.0005 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-08-31.

CI and CD Cloud DevOps and cloud

mirrord-prev-env

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…

metalbear-co/mirrord · 122 tokens

mirrord-chaos

Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…

metalbear-co/mirrord · 119 tokens

deploy