cicd-pipelines

A toolkit for designing software delivery pipelines. CI/CD means automatically checking, building, scanning, and releasing code when changes are made.

In plain words
What is it for?
Use it to design pipelines for systems such as GitHub Actions, GitLab CI, or Jenkins, including infrastructure setup, security checks, and deployment automation.
Why use it?
It helps teams plan repeatable releases and reduce manual deployment work. It also covers infrastructure as code, where servers and cloud resources are described in files, and GitOps, where Git changes control deployments.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add viktorbezdek/skillstack
agentmods
npx agentmods add plugins/viktorbezdek/skillstack/cicd-pipelines
Clone the repo
git clone --depth 1 https://github.com/viktorbezdek/skillstack

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

cicd-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 2d 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.

cicd-pipelines/.claude-plugin/plugin.json · 21 lines

What it actually says

{
  "name": "cicd-pipelines",
  "version": "1.1.24",
  "description": "Comprehensive CI/CD pipeline design, DevOps automation, infrastructure as code, GitOps deployment automation, security scanning, and enterprise pipeline readiness.",
  "author": {
    "name": "Viktor Bezdek",
    "url": "https://github.com/viktorbezdek"
  },
  "license": "MIT",
  "repository": "https://github.com/viktorbezdek/skillstack/tree/main/cicd-pipelines",
  "keywords": [
    "claude-code",
    "skill",
    "CI/CD",
    "GitHub Actions",
    "GitLab CI",
    "Jenkins",
    "Terraform"
  ]
}
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. 2d ago First seen · 21 lines scan A 590ae3c8642b

Subscribe to this mod's changes

cicd-pipelines is a plugin published in the GitHub repository viktorbezdek/skillstack (11 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.