ci-cd-pipelines

ci-cd-pipelines is a skill for Claude Code from MonumentalSystems/Atlas-Agent-Teams. It costs 29 tokens per session (2,800 once invoked), scanned A, original, MIT.

A guide to setting up automated build, test, and deployment processes for software projects. It covers GitHub Actions, GitLab CI/CD, Jenkins, and Azure DevOps.

In plain words
What is it for?
Use it to design CI/CD workflows, organize jobs and reusable steps, speed up builds, pass artifacts between jobs, and protect deployments.
Why use it?
It helps replace manual release steps with repeatable workflows that run when code changes. It also addresses testing across configurations, dependency caching, secrets, and deployment safeguards.

Skill for Claude Code

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

Part of the devops-cloud plugin — 4 skills, 1 command, 5 agents shipped together

Good fit Use it to design CI/CD workflows, organize jobs and reusable steps, speed up builds, pass artifacts between jobs, and protect deployments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/monumentalsystems/atlas-agent-teams/ci-cd-pipelines
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 MonumentalSystems/Atlas-Agent-Teams --skill ci-cd-pipelines
Clone the repo
git clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-Teams

Made for: Claude Code.

Or install devops-cloud, the plugin that ships this one along with the rest of its 4 skills, 1 command, 5 agents.

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-pipelines

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/ci-cd-pipelines"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/ci-cd-pipelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,800 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
  • NVIDIA SkillSpector pass 7 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.02800
Opus 5 $0.00015 $0.01400
Sonnet 5 $0.00006 $0.00560
Haiku 4.5 $0.00003 $0.00280

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

Security

Grade A, and why

ci-cd-pipelines 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 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.

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.

teams/devops-cloud/skills/ci-cd-pipelines/SKILL.md · 436 lines

How it starts

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

CI/CD Pipelines

GitHub Actions Workflows

Core Concepts

  • Workflows: YAML files defining automation processes
  • Events: Triggers for workflow execution (push, pull_request, schedule)
  • Jobs: Collections of steps that run on the same runner
  • Steps: Individual tasks within a job
  • Actions: Reusable components for common tasks

Best Practices

  • Workflow Organization

    • Use separate workflows for different concerns (CI, CD, release)
    • Use workflow templates for consistency
    • Use composite actions for reusable steps
    • Use reusable workflows for shared pipeline logic
    • Use matrix strategy for testing across multiple configurations
  • Job Optimization

    • Use caching for dependencies and build artifacts
    • Use parallel jobs for faster execution
    • Use job dependencies for sequential execution
    • Use artifacts for passing data between jobs
    • Use self-hosted runners for custom environments
  • Security

    • Use secrets for sensitive data
    • Use environments for deployment protection
    • Use required reviews for critical deployments
    • Use OIDC for cloud provider authentication
    • Use branch protection rules

GitHub Actions Examples

name: CI/CD Pipeline

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

jobs:
  test:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        node-version: [14.x, 16.x, 18.x]
    steps:
      - uses: actions/checkout@v3
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v3
        with:
          node-version: ${{ matrix.node-version }}
          cache: 'npm'
      - run: npm ci
      - run: npm test
      - run: npm run build

  deploy:
    needs: test
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main'
    steps:
      - uses: actions/checkout@v3
      - name: Deploy to production
        run: |
          # Deployment commands

GitLab CI/CD Pipelines

Core Concepts

  • Pipelines: Series of jobs executed in stages
  • Stages: Logical grouping of jobs
  • Jobs: Individual tasks that execute scripts
  • Runners: Agents that execute jobs
  • Artifacts: Files passed between jobs

Read the full file on GitHub · 436 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 · 436 lines · 29 tokens per session scan A ebdeef4092ec

Subscribe to this mod's changes

ci-cd-pipelines is a skill published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 2,800 once invoked, about $0.0001 per session on Opus 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.

Related

Other skills, from other repositories

import-prom-rule

Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…

ccfos/nightingale · 125 tokens

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

atmos-profiles

Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.

cloudposse/atmos · 35 tokens

webhook-management

Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.

hoangsonww/Claude-Code-Agent-Monitor · 56 tokens

managing-github-actions-secrets

Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.

PostHog/posthog-foss · 67 tokens