deployment-pipeline-design

deployment-pipeline-design is a skill for Claude Code from HermeticOrmus/claude-code-game-development. It costs 41 tokens per session (2,071 once invoked), scanned A, a copy of deployment-pipeline-design, MIT.

Guidance for designing CI/CD pipelines, which automatically build, test, and deliver software. It covers stages such as staging, approvals, production deployment, health checks, and rollback.

In plain words
What is it for?
Use it to plan multi-environment pipelines, approval gates, progressive delivery, GitOps workflows, verification, and automated rollback.
Why use it?
It helps teams release changes in controlled steps while adding security checks and ways to recover from failed deployments.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the cicd-automation plugin — 4 skills shipped together

Good fit Use it to plan multi-environment pipelines, approval gates, progressive delivery, GitOps workflows, verification, and automated rollback.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hermeticormus/claude-code-game-development/deployment-pipeline-design
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 HermeticOrmus/claude-code-game-development --skill deployment-pipeline-design
Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/claude-code-game-development

Made for: Claude Code.

Or install cicd-automation, the plugin that ships this one along with the rest of its 4 skills.

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-pipeline-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/hermeticormus/claude-code-game-development/deployment-pipeline-design.svg)](https://agentmods.dev/skills/hermeticormus/claude-code-game-development/deployment-pipeline-design)
Your own site
<a href="https://agentmods.dev/skills/hermeticormus/claude-code-game-development/deployment-pipeline-design"><img src="https://agentmods.dev/badge/skills/hermeticormus/claude-code-game-development/deployment-pipeline-design.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 2,071 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod 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.00041 $0.02071
Opus 5 $0.00020 $0.01035
Sonnet 5 $0.00008 $0.00414
Haiku 4.5 $0.00004 $0.00207

Measured 8d ago against content hash 0c7343294b6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

deployment-pipeline-design scanned grade A with 1 finding 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 8d 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.

Makes network callslowCapability

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

run: curl -f https://app.example.com/health
Origin

This is a copy

91% identical to deployment-pipeline-design — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/cicd-automation/skills/deployment-pipeline-design/SKILL.md · 360 lines

How it starts

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

Deployment Pipeline Design

Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies.

Purpose

Design robust, secure deployment pipelines that balance speed with safety through proper stage organization and approval workflows.

When to Use

  • Design CI/CD architecture
  • Implement deployment gates
  • Configure multi-environment pipelines
  • Establish deployment best practices
  • Implement progressive delivery

Pipeline Stages

Standard Pipeline Flow

┌─────────┐   ┌──────┐   ┌─────────┐   ┌────────┐   ┌──────────┐
│  Build  │ → │ Test │ → │ Staging │ → │ Approve│ → │Production│
└─────────┘   └──────┘   └─────────┘   └────────┘   └──────────┘

Detailed Stage Breakdown

  1. Source - Code checkout
  2. Build - Compile, package, containerize
  3. Test - Unit, integration, security scans
  4. Staging Deploy - Deploy to staging environment
  5. Integration Tests - E2E, smoke tests
  6. Approval Gate - Manual approval required
  7. Production Deploy - Canary, blue-green, rolling
  8. Verification - Health checks, monitoring
  9. Rollback - Automated rollback on failure

Approval Gate Patterns

Pattern 1: Manual Approval

# GitHub Actions
production-deploy:
  needs: staging-deploy
  environment:
    name: production
    url: https://app.example.com
  runs-on: ubuntu-latest
  steps:
    - name: Deploy to production
      run: |
        # Deployment commands

Pattern 2: Time-Based Approval

# GitLab CI
deploy:production:
  stage: deploy
  script:
    - deploy.sh production
  environment:
    name: production
  when: delayed
  start_in: 30 minutes
  only:
    - main

Pattern 3: Multi-Approver

# Azure Pipelines
stages:
- stage: Production
  dependsOn: Staging
  jobs:
  - deployment: Deploy
    environment:
      name: production
      resourceType: Kubernetes
    strategy:
      runOnce:
        preDeploy:
          steps:
          - task: ManualValidation@0
            inputs:
              notifyUsers: '[email protected]'
              instructions: 'Review staging metrics before approving'

Read the full file on GitHub · 360 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. 8d ago First seen · 360 lines · 41 tokens per session scan A 0c7343294b6f

Subscribe to this mod's changes

deployment-pipeline-design is a skill published in the GitHub repository HermeticOrmus/claude-code-game-development (62 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 2,071 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to deployment-pipeline-design, differing in 19 lines, and is treated as a copy.