What is cicd-pipeline-setup?

A guide for creating automated workflows that test, build, check, and deploy software using services such as GitHub Actions, GitLab CI, Jenkins, or CircleCI. CI/CD means automatically checking and delivering code changes.

Use it to set up workflows for automated tests, container builds, security scans, release versioning, artifact storage, and multi-environment deployments.

It removes much of the repeated manual work involved in testing releases and deploying them to different environments. It also helps include security and performance checks in the delivery process.

cicd-pipeline-setup — Skill for Claude Code and Codex by aj-geddes

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 aj-geddes/useful-ai-prompts --skill cicd-pipeline-setup

Clone the repo

git clone --depth 1 https://github.com/aj-geddes/useful-ai-prompts

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/aj-geddes/useful-ai-prompts/cicd-pipeline-setup/github.svg)](https://agentmods.dev/skills/aj-geddes/useful-ai-prompts/cicd-pipeline-setup)

Your own site

<a href="https://agentmods.dev/skills/aj-geddes/useful-ai-prompts/cicd-pipeline-setup"><img src="https://agentmods.dev/badge/skills/aj-geddes/useful-ai-prompts/cicd-pipeline-setup/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/aj-geddes/useful-ai-prompts/cicd-pipeline-setup"><img src="https://agentmods.dev/badge/skills/aj-geddes/useful-ai-prompts/cicd-pipeline-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 525 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

Socket warn 16 Sept 2026
Snyk pass 16 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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.00525
Opus 5.5	$0.00016	$0.00210
Sonnet 5.5	$0.00008	$0.00105
Haiku 4.5	$0.00004	$0.00052

Measured 2mo ago against content hash d0d7eecd7749, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cicd-pipeline-setup 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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/validate-pipeline.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.

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.

skills/cicd-pipeline-setup/SKILL.md · 99 lines

How it starts

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

Overview

Build automated continuous integration and deployment pipelines that test code, build artifacts, run security checks, and deploy to multiple environments with minimal manual intervention.

When to Use

Automated code testing and quality checks
Containerized application builds
Multi-environment deployments
Release management and versioning
Automated security scanning
Performance testing integration
Artifact management and registry

Quick Start

Minimal working example:

# .github/workflows/deploy.yml
name: Build and Deploy

on:
  push:
    branches:
      - main
      - develop
  pull_request:
    branches:
      - main
  workflow_dispatch:

env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}

jobs:
  test:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        node-version: [18.x, 20.x]

    steps:
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

Guide	Contents
GitHub Actions Workflow	GitHub Actions Workflow
GitLab CI Pipeline	GitLab CI Pipeline
Jenkins Pipeline	Jenkins Pipeline
CI/CD Script	CI/CD Script

Best Practices

✅ DO

Fail fast with early validation
Run tests in parallel when possible
Use caching for dependencies
Implement proper secret management
Gate production deployments with approval
Monitor and alert on pipeline failures
Use consistent environment configuration
Implement infrastructure as code

❌ DON'T

Store credentials in pipeline configuration
Deploy without automated tests
Skip security scanning
Allow long-running pipelines
Mix staging and production pipelines
Ignore test failures
Deploy directly to main branch
Skip health checks after deployment

Read the full file on GitHub · 99 lines

Files

What ships with it

6 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.

2mo ago First seen · 99 lines · 40 tokens per session scan A d0d7eecd7749

Subscribe to this mod's changes

cicd-pipeline-setup is a skill published in the GitHub repository aj-geddes/useful-ai-prompts (376 stars, last pushed 8mo ago), licensed MIT. It adds 40 tokens to every session and 525 once invoked, about $0.0002 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-30.

CI and CD DevOps and cloud Testing

cicd-pipeline-setup next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cicd-pipeline-setupaj-geddes/useful-ai-prompts	Skill	376	8mo ago	MIT	A	40	Claude Code, Codex
chinese-git-workflowjnMetaCode/superpowers-zh	Skill	8.5k	11d ago	MIT	A	69	Claude Code
atmos-profilescloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	35	Claude Code
webhook-managementhoangsonww/Claude-Code-Agent-Monitor	Skill	1.1k	yesterday	MIT	A	56	Claude Code, Codex
monorepo-managementwshobson/agents	Skill	42k	yesterday	MIT	C	54	Claude Code
managing-github-actions-secretsPostHog/posthog-foss	Skill	728	yesterday	MIT	A	67	Claude Code, Codex
postman-newman-automationLambdaTest/agent-skills	Skill	390	yesterday	MIT	A	156	Claude Code, Codex

cicd-pipeline-setup