ci-cd-pipeline

ci-cd-pipeline is a skill for Claude Code from nasrulhazim/claude. It costs 316 tokens per session (4,301 once invoked), scanned D, original, MIT.

A CI/CD builder for Laravel projects. CI checks code automatically, while CD automates delivery to staging or production environments.

In plain words
What is it for?
Use it to add staging and production deployment, Docker containerisation, VPS or container-registry deployment, and GitHub Actions secret guidance.
Why use it?
It extends existing GitHub Actions checks with deployment workflows, Docker files, deployment settings, secret-management guidance, and failure notifications.

Skill for Claude Code

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

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

Part of the claude-toolkit plugin — 36 skills, 12 commands, 20 agents shipped together

Good fit Use it to add staging and production deployment, Docker containerisation, VPS or container-registry deployment, and GitHub Actions secret guidance.

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/nasrulhazim/claude
agentmods
npx agentmods add skills/nasrulhazim/claude/ci-cd-pipeline

Made for: Claude Code.

Or install claude-toolkit, the plugin that ships this one along with the rest of its 36 skills, 12 commands, 20 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-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/nasrulhazim/claude/ci-cd-pipeline/github.svg)](https://agentmods.dev/skills/nasrulhazim/claude/ci-cd-pipeline)
Your own site
<a href="https://agentmods.dev/skills/nasrulhazim/claude/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/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/nasrulhazim/claude/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/ci-cd-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 316 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,301 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. 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.00316 $0.04301
Opus 5 $0.00158 $0.02150
Sonnet 5 $0.00063 $0.00860
Haiku 4.5 $0.00032 $0.00430

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

Security

Grade D, and why

ci-cd-pipeline scanned grade D with 2 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 8d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo systemctl reload php8.3-fpm

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

ls -dt */ | tail -n +6 | xargs rm -rf
skills/ci-cd-pipeline/SKILL.md · 543 lines

How it starts

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

CI/CD Pipeline Builder

Continuous deployment pipelines, Docker containerisation, and deployment automation for Laravel projects. Built on top of Laravel Kickoff's existing GitHub Actions CI and /bin scripts.

Command Reference

Command Description
/ci extend Extend Kickoff's CI with CD pipeline (staging + production deploy)
/ci docker Generate Dockerfile, docker-compose.yml, and .dockerignore for Laravel
/ci deploy Deployment configs for VPS via SSH or container registry
/ci secrets Secret management guidance for GitHub Actions and deployment

Kickoff Baseline

Laravel Kickoff projects ship with these CI/CD foundations already configured:

GitHub Actions CI (already exists)

Tool Workflow Step Purpose
Pint pint --test Code style enforcement
PHPStan / Larastan phpstan analyse Static analysis
Rector rector --dry-run Automated refactoring checks
Pest php artisan test Test suite execution

/bin Scripts (already exist)

Script Purpose
bin/deploy.sh Pull latest code, install deps, run migrations, restart services
bin/backup.sh Database dump + file backup before deployments
bin/setup.sh First-time server setup (packages, permissions, cron, queue)

This skill extends the baseline — it does not replace it. All CI steps remain; CD steps are added after successful CI.


1. /ci extend — Add CD Pipeline to Existing CI

Step 1: Assess Current Setup

Read the existing .github/workflows/ directory. Identify:

  • Which CI steps already run (Pint, PHPStan, Rector, Pest)
  • Whether any CD steps already exist
  • The branch strategy (main, develop, staging branches)

Ask the user:

  • What is your deployment target? (VPS via SSH / Docker registry / both)
  • Do you have separate staging and production environments?
  • What branch triggers each environment? (default: develop -> staging, main -> production)

Read the full file on GitHub · 543 lines

Files

What ships with it

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

  1. 8d ago Changed · +41 lines d4f7301d9253
  2. 12d ago First seen · 502 lines · 316 tokens per session scan D e3f26254c336

Subscribe to this mod's changes

ci-cd-pipeline is a skill published in the GitHub repository nasrulhazim/claude (23 stars, last pushed 9d ago), licensed MIT. It adds 316 tokens to every session and 4,301 once invoked, about $0.0016 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). 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

deployment-patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

affaan-m/ECC · 41 tokens

nextjs-deployment

Provides comprehensive patterns for deploying Next.js applications to production. Use when configuring Docker containers, setting up GitHub Actions CI/CD pipelines, managing environment variables, implementing preview deployments, or setting up monitoring and logging for Next.js applications. Covers standalone output…

giuseppe-trisciuoglio/developer-kit · 71 tokens

devops

DevOps - Docker, CI/CD, cloud infra, monitoring.

sipyourdrink-ltd/bernstein · 16 tokens

performing-container-security-scanning-with-trivy

Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.

xalgorix/xalgorix · 48 tokens

devops-deployment

Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.

yonatangross/orchestkit · 44 tokens

devops-infrastructure

Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.

CloudAI-X/claude-workflow-v2 · 57 tokens