ci-cd-and-automation

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

Guidance for setting up automated checks and release pipelines. CI/CD means automatically testing, checking, building, and deploying software as changes move toward production.

In plain words
What is it for?
Use it to configure linting, type checks, tests, builds, deployment steps, quality gates, and troubleshooting for failed CI runs.
Why use it?
It catches problems consistently before changes are merged or released, reducing the chance that broken code reaches users.

Skill for Claude CodeCodex

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

Good fit Use it to configure linting, type checks, tests, builds, deployment steps, quality gates, and troubleshooting for failed CI runs.

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

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/kevinnft/ai-agent-skills/ci-cd-and-automation/github.svg)](https://agentmods.dev/skills/kevinnft/ai-agent-skills/ci-cd-and-automation)
Your own site
<a href="https://agentmods.dev/skills/kevinnft/ai-agent-skills/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/kevinnft/ai-agent-skills/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/kevinnft/ai-agent-skills/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/kevinnft/ai-agent-skills/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,767 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 95% 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.02767
Opus 5 $0.00023 $0.01384
Sonnet 5 $0.00009 $0.00553
Haiku 4.5 $0.00005 $0.00277

Measured 12d ago against content hash 4db7a04f550f, 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-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 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.

Origin

This is a copy

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

skills/addyosmani/ci-cd-and-automation/SKILL.md · 396 lines

How it starts

The opening of the file, as written. The whole thing — 396 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: addyosmani-ci-cd

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 · 396 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 · 396 lines · 45 tokens per session scan A 4db7a04f550f

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

playwright-ci

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

testdino-hq/playwright-skill · 48 tokens

040101-docker-deploy

Docker deployment patterns for web applications — multi-stage builds, environment management, CI/CD integration, and self-hosting strategies.

natuleadan/skills · 31 tokens

devsecops-checker

Review CI or CD pipeline configuration for DevSecOps controls and help Claude explain maturity gaps, missing safeguards, and practical improvements.

maxwellokumu/okaudit-claude-skills · 31 tokens

component-family-consistency

Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library…

dembrandt/dembrandt-skills · 76 tokens

brand-visual-language

A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…

dembrandt/dembrandt-skills · 68 tokens

loading-states-and-perceived-performance

Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…

dembrandt/dembrandt-skills · 68 tokens