agentmods.dev

deployment

deployment is a skill for Claude Code, Codex from infohata/mind-vault. It costs 41 tokens per session (8,192 once invoked), scanned D, original, Apache-2.0.

A deployment procedure for putting Docker Compose web applications into production. Docker Compose runs an application's containers together; production is the live environment used by customers.

In plain words
What is it for?
Use it to prepare or run a production deployment, set up deployment and backup scripts, configure SSL with Let's Encrypt, connect CI/CD, verify health, or roll back a failed release.
Why use it?
It adds checks around backups, database changes, remote commands, failed releases, and site health, while making the expected short outage during an update clear.

Skill for Claude CodeCodex

Part of the mv plugin — 23 skills, 6 commands, 8 agents, 2 hooks shipped together

not rated 2 changed today D scan 41 tokens original Apache-2.0
View the source file infohata/mind-vault
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/infohata/mind-vault/deployment
Any agent
npx skills add infohata/mind-vault --skill deployment
Clone the repo
git clone --depth 1 https://github.com/infohata/mind-vault

Made for: Claude Code, Codex.

Or install mv, the plugin that ships this one along with the rest of its 23 skills, 6 commands, 8 agents, 2 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 deployment

README.md
[![agentmods](https://agentmods.dev/badge/skills/infohata/mind-vault/deployment.svg)](https://agentmods.dev/skills/infohata/mind-vault/deployment)
Your own site
<a href="https://agentmods.dev/skills/infohata/mind-vault/deployment"><img src="https://agentmods.dev/badge/skills/infohata/mind-vault/deployment.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,192 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 3 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.00041 $0.08192
Opus 5 $0.00020 $0.04096
Sonnet 5 $0.00008 $0.01638
Haiku 4.5 $0.00004 $0.00819

Measured today against content hash 0f9910390011, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

deployment scanned grade D with 3 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 today.

The scan reads SKILL.md. This mod also ships 8 executable files (scripts/backup_db.sh, scripts/deploy_first_time.sh, scripts/deploy_update.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- [references/SHELL_INSTALLERS.md](references/SHELL_INSTALLERS.md) — authoring + review patterns for `install/install-*.sh` **and remote-sudo / forced-command wrappers**; installer-specific catalog (chown, marker blocks,

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

- SSH key perms: `chmod 600 ~/.ssh/id_rsa`.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsI https://${DOMAIN} # external HTTPS reachable
skills/deployment/SKILL.md · 496 lines

How it starts

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

deployment

Production deployment pattern for containerised web applications using Docker Compose. Prioritises safety (automatic backups before destructive steps, rollback-ready state, mandatory screen sessions for remote runs) over raw speed. This is not a zero-downtime pattern — it's a stop/rebuild/start cycle with health verification. Brief outages (5–30 s) are expected on updates.

This skill covers:

  • Branch strategy and release management
  • Change-aware deploy scripts (migrations, dependencies, static assets)
  • Database safety (pre-change backups, rollback procedures)
  • Remote SSH deployment with mandatory screen sessions
  • Let's Encrypt SSL via certbot + nginx
  • Health checks and deployment verification
  • Environment management and .env handling
  • Makefile targets for common operations

When to use

TRIGGER when: preparing or executing a production deploy for a Docker Compose application; setting up the initial deploy.sh + backup_db.sh + verify_deployment.sh toolchain; wiring a CI/CD pipeline that invokes the deploy scripts; handling rollback after a failed deploy.

SKIP for: local dev-container startup (docker compose up), single-container toy apps, Kubernetes-based deploys (different contract — use Helm/ArgoCD), PaaS targets (Heroku/Fly/Railway — they own their own deploy verb and these scripts will conflict).

Pattern

Branch strategy

Separate production from development:

  • Use a deployment (or production) branch for releases.
  • Merge stable commits from main into deployment explicitly — no auto-fast-forward.
  • Branch protection on deployment: require review, disallow force-push.
  • A clear commit boundary on the release branch = a clean rollback target.
git checkout deployment
git merge <stable-sha>
git push origin deployment

Service architecture

Typical Docker Compose stack:

Service Role
web Application container (Django, Rails, Node, …)
nginx Reverse proxy, SSL termination, static file serving
db PostgreSQL / MySQL
cache Redis / Memcached
worker Background jobs (Celery / Sidekiq / BullMQ)
certbot Let's Encrypt renewals
storage (opt.) MinIO / S3-compatible object store

Read the full file on GitHub · 496 lines

Files

What ships with it

26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. today Changed 0f9910390011
  2. 4d ago First seen · 496 lines · 41 tokens per session scan D 1f5d0d3df3b8

Subscribe to this mod's changes

deployment is a skill published in the GitHub repository infohata/mind-vault (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 8,192 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

CloudContainersDevOps and cloud
Related

Other skills, from other repositories

openshell-cli

Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and inference routing. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox…

NVIDIA/OpenShell · 127 tokens

langbot-deploy

Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…

langbot-app/LangBot · 104 tokens

azure-cloud-migrate

Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…

microsoft/skills · 106 tokens

compute-env-setup

Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.

companion-inc/feynman · 45 tokens

atmos-helmfile

Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.

cloudposse/atmos · 33 tokens

atmos-devcontainer

Devcontainer orchestration: start/stop/attach/shell/exec/rebuild, instance management, config handling, VS Code integration.

cloudposse/atmos · 31 tokens