ci-cd-and-automation

ci-cd-and-automation is a skill for Claude Code, Codex from stefaniuk/loadout. It costs 45 tokens per session (2,719 once invoked), scanned A, a copy of ci-cd-and-automation, MIT.

A setup and maintenance guide for CI/CD, the automated checks and delivery steps that run when software changes. It covers pipelines for testing, building, and deploying software.

In plain words
What is it for?
It helps configure linting, type checks, tests, builds, deployment steps, and responses to CI failures.
Why use it?
It makes quality checks run consistently and helps prevent changes from reaching production without passing required checks.

Skill for Claude CodeCodex

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

Good fit It helps configure linting, type checks, tests, builds, deployment steps, and responses to CI failures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stefaniuk/loadout/ci-cd-and-automation
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 stefaniuk/loadout --skill ci-cd-and-automation
Clone the repo
git clone --depth 1 https://github.com/stefaniuk/loadout

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-and-automation

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/stefaniuk/loadout/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/stefaniuk/loadout/ci-cd-and-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,719 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.
Origin 100% 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.00045 $0.02719
Opus 5 $0.00023 $0.01359
Sonnet 5 $0.00009 $0.00544
Haiku 4.5 $0.00005 $0.00272

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

Security

Grade A, and why

ci-cd-and-automation 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 9d 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.

Origin

This is a copy

100% identical to ci-cd-and-automation — 0 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.

.github/skills/ci-cd-and-automation/SKILL.md · 391 lines

How it starts

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

CI/CD and Automation

Overview

Automate quality gates so that no change reaches production without passing tests, lint, type checking, and build. CI/CD is the enforcement mechanism for every other skill — it catches what humans and agents miss, and it does so consistently on every single change.

Shift Left: Catch problems as early in the pipeline as possible. A bug caught in linting costs minutes; the same bug caught in production costs hours. Move checks upstream — static analysis before tests, tests before staging, staging before production.

Faster is Safer: Smaller batches and more frequent releases reduce risk, not increase it. A deployment with 3 changes is easier to debug than one with 30. Frequent releases build confidence in the release process itself.

When to Use

  • Setting up a new project's CI pipeline
  • Adding or modifying automated checks
  • Configuring deployment pipelines
  • When a change should trigger automated verification
  • Debugging CI failures

The Quality Gate Pipeline

Every change goes through these gates before merge:

Pull Request Opened
    │
    ▼
┌─────────────────┐
│   LINT CHECK     │  eslint, prettier
│   ↓ pass         │
│   TYPE CHECK     │  tsc --noEmit
│   ↓ pass         │
│   UNIT TESTS     │  jest/vitest
│   ↓ pass         │
│   BUILD          │  npm run build
│   ↓ pass         │
│   INTEGRATION    │  API/DB tests
│   ↓ pass         │
│   E2E (optional) │  Playwright/Cypress
│   ↓ pass         │
│   SECURITY AUDIT │  npm audit
│   ↓ pass         │
│   BUNDLE SIZE    │  bundlesize check
└─────────────────┘
    │
    ▼
  Ready for review

No gate can be skipped. If lint fails, fix lint — don't disable the rule. If a test fails, fix the code — don't skip the test.

GitHub Actions Configuration

Basic CI Pipeline

# .github/workflows/ci.yml
name: CI

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

jobs:
  quality:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: '22'
          cache: 'npm'

      - name: Install dependencies
        run: npm ci

      - name: Lint
        run: npm run lint

      - name: Type check
        run: npx tsc --noEmit

      - name: Test
        run: npm test -- --coverage

      - name: Build
        run: npm run build

      - name: Security audit
        run: npm audit --audit-level=high

Read the full file on GitHub · 391 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. 9d ago First seen · 391 lines · 45 tokens per session scan A a6ed8ed56456

Subscribe to this mod's changes

ci-cd-and-automation is a skill published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 2,719 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ci-cd-and-automation, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

artifact-conventions

Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/ / to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.

attilaszasz/sdd-pilot · 59 tokens

plan-authoring

Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.

attilaszasz/sdd-pilot · 41 tokens

task-generation

Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.

attilaszasz/sdd-pilot · 35 tokens

adr-authoring

Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.

attilaszasz/sdd-pilot · 30 tokens

implementation-standards

Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.

attilaszasz/sdd-pilot · 44 tokens

spec-authoring

Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by specify-feature; not directly invokable.

attilaszasz/sdd-pilot · 40 tokens