ci-cd-pipeline

ci-cd-pipeline is a skill for Claude Code, Codex from furkangonel/cowrangler. It costs 18 tokens per session (2,368 once invoked), scanned A, original, MIT.

A guide for designing and implementing CI/CD pipelines, which automatically check, build, and deliver software. It covers common services such as GitHub Actions, GitLab, and CircleCI.

In plain words
What is it for?
Setting up or debugging pipelines for linting, tests, builds, security checks, staging, production deployment, smoke tests, and notifications.
Why use it?
It gives automated checks and deployments a clear order, so problems can stop a release before they reach production.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is uses: ./.github/workflows/reusable-deploy.yml.

Good fit Setting up or debugging pipelines for linting, tests, builds, security checks, staging, production deployment, smoke tests, and notifications.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/furkangonel/cowrangler
agentmods
npx agentmods add skills/furkangonel/cowrangler/ci-cd-pipeline

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.

agentmods badge for ci-cd-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/furkangonel/cowrangler/ci-cd-pipeline/github.svg)](https://agentmods.dev/skills/furkangonel/cowrangler/ci-cd-pipeline)
Your own site
<a href="https://agentmods.dev/skills/furkangonel/cowrangler/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/furkangonel/cowrangler/ci-cd-pipeline/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.

agentmods 80×15 button for ci-cd-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/furkangonel/cowrangler/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/furkangonel/cowrangler/ci-cd-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,368 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 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.1 $0.00018 $0.02368
Opus 5 $0.00009 $0.01184
Sonnet 5 $0.00004 $0.00474
Haiku 4.5 $0.00002 $0.00237

Measured 12d ago against content hash 9242a3d9e372, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ci-cd-pipeline 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 12d 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://green.example.com/health
bundled_skills/devops/ci-cd-pipeline/SKILL.md · 340 lines

How it starts

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

CI/CD Pipeline SOP

When to Use

  • User wants to set up CI/CD for a project
  • User asks about GitHub Actions, GitLab CI, CircleCI, or similar tools
  • User wants to automate testing, building, or deployment
  • User's pipeline is failing and they need to debug it

Part 1 — Pipeline Anatomy

Every solid pipeline has these stages in order:

Trigger → Lint → Test → Build → Security Scan → Deploy → Notify
Stage Purpose Fail behavior
Lint Code style, static analysis Block PR merge
Test Unit + integration tests Block PR merge
Build Compile / package / containerize Block PR merge
Security Scan SAST, dependency audit, secret detection Block or warn
Deploy: Staging Push to staging environment Block prod deploy
Smoke Test Quick sanity check on staging Block prod deploy
Deploy: Prod Production release Notify team

Part 2 — GitHub Actions Templates

Template A — Node.js Full Pipeline

name: CI/CD

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main, develop]

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true      # cancel in-flight runs on new push

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

jobs:
  # ─── Lint ────────────────────────────────────────────────────────
  lint:
    name: Lint & Type Check
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: ${{ env.NODE_VERSION }}
          cache: "npm"
      - run: npm ci
      - run: npm run lint
      - run: npm run type-check

  # ─── Test ────────────────────────────────────────────────────────
  test:
    name: Unit & Integration Tests
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:16-alpine
        env:
          POSTGRES_USER: testuser
          POSTGRES_PASSWORD: testpass
          POSTGRES_DB: testdb
        ports: ["5432:5432"]
        options: >-
          --health-cmd pg_isready
          --health-interval 10s
          --health-timeout 5s
          --health-retries 5
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: ${{ env.NODE_VERSION }}
          cache: "npm"
      - run: npm ci
      - run: npm test -- --coverage
        env:
          DATABASE_URL: postgresql://testuser:testpass@localhost:5432/testdb
      - uses: codecov/codecov-action@v4
        with:
          token: ${{ secrets.CODECOV_TOKEN }}

  # ─── Build & Push Docker Image ───────────────────────────────────
  build:
    name: Build Docker Image
    needs: [lint, test]
    runs-on: ubuntu-latest
    outputs:
      image-tag: ${{ steps.meta.outputs.tags }}
      image-digest: ${{ steps.build.outputs.digest }}
    permissions:
      contents: read
      packages: write
    steps:
      - uses: actions/checkout@v4
      - uses: docker/setup-buildx-action@v3
      - uses: docker/login-action@v3
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
      - uses: docker/metadata-action@v5
        id: meta
        with:
          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
          tags: |
            type=sha,prefix=sha-
            type=ref,event=branch
            type=semver,pattern={{version}}
      - uses: docker/build-push-action@v5
        id: build
        with:
          context: .
          push: true
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          cache-from: type=gha
          cache-to: type=gha,mode=max

  # ─── Deploy to Staging ───────────────────────────────────────────
  deploy-staging:
    name: Deploy → Staging
    needs: build
    runs-on: ubuntu-latest
    environment:
      name: staging
      url: https://staging.example.com
    if: github.ref == 'refs/heads/develop'
    steps:
      - name: Deploy to staging
        run: |
          echo "Deploying ${{ needs.build.outputs.image-tag }} to staging"
          # kubectl set image deployment/app app=${{ needs.build.outputs.image-tag }}
          # or: ssh deploy@staging "docker pull ... && docker-compose up -d"

  # ─── Deploy to Production ────────────────────────────────────────
  deploy-prod:
    name: Deploy → Production
    needs: [build, deploy-staging]
    runs-on: ubuntu-latest
    environment:
      name: production
      url: https://example.com
    if: github.ref == 'refs/heads/main'
    steps:
      - name: Deploy to production
        run: |
          echo "Deploying to production"

Read the full file on GitHub · 340 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. 12d ago First seen · 340 lines · 18 tokens per session scan A 9242a3d9e372

Subscribe to this mod's changes

ci-cd-pipeline is a skill published in the GitHub repository furkangonel/cowrangler (2 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 2,368 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

ci-cd-pipeline-generator

Generate production-ready CI/CD pipeline configurations for GitHub Actions, GitLab CI, CircleCI, and Jenkins. Activates when users ask to set up CI/CD, create deployment pipelines, automate build/test/deploy workflows, configure Docker builds, set up staging/production environments, or add quality gates. Covers…

JPeetz/agent-skills · 135 tokens

CI/CD Pipeline Advanced

Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.

PramodDutta/qaskills · 45 tokens

cicd-expert

Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation. Use when the user mentions CI/CD, GitHub Actions, Jenkins, GitLab CI, deployment, or automation, or when the task involves CI/CD Fundamentals, Pipeline Design, Workflow Basics, or Docker Build and Push.

personamanagmentlayer/pcl · 67 tokens

CI/CD Pipeline Config

CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.

PramodDutta/qaskills · 35 tokens

github-release-management

GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.

frankxai/claude-skills-library · 43 tokens

ci-cd-pipeline

Create and optimize CI/CD pipelines with GitHub Actions, automated testing, deployment, and release workflows. Use when setting up continuous integration, deployment automation, or improving build pipelines.

asgarovf/locusai · 41 tokens