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.
npx agentmods add skills/kraitdev/skill.md/ci-cd-pipeline-architecturenpx skills add KraitDev/skiLL.Md --skill ci-cd-pipeline-architecturegit clone --depth 1 https://github.com/KraitDev/skiLL.MdWrote 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.
[](https://agentmods.dev/skills/kraitdev/skill.md/ci-cd-pipeline-architecture)<a href="https://agentmods.dev/skills/kraitdev/skill.md/ci-cd-pipeline-architecture"><img src="https://agentmods.dev/badge/skills/kraitdev/skill.md/ci-cd-pipeline-architecture.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00022 | $0.01733 |
| Opus 5 | $0.00011 | $0.00866 |
| Sonnet 5 | $0.00004 | $0.00347 |
| Haiku 4.5 | $0.00002 | $0.00173 |
Grade A, and why
ci-cd-pipeline-architecture 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Pipeline Architecture
Purpose
Pipelines are the line between "works on my machine" and "production is down." This skill ensures code is built exactly once, tested comprehensively, and deployed reliably through immutable artifacts without human intervention.
When to use
- Setting up a new GitHub Actions, GitLab CI, or Jenkins workflow
- Automating manual deployment processes
- Enforcing code quality checks on Pull Requests
- Establishing environment promotion strategy (dev → staging → production)
When NOT to use
- Local development builds (use Makefile or npm scripts)
- Manual hotfixes (always use pipeline)
Inputs required
- Git repository with configured CI/CD platform (GitHub Actions, GitLab CI, Jenkins)
- Build/test environment specifications
- Environment configurations (dev, staging, prod)
- Secret management platform access
Workflow
- Trigger Definition: Define strict triggers. Run tests/linters on
pull_request. Run builds/deployments onpushtomainor uponreleasetags. - Fail Fast: Order jobs sequentially by speed. Run Linters, Type Checkers first. If they fail, halt before running expensive test suites.
- Automate Testing: Run unit and integration tests inside isolated, ephemeral containers (e.g., Docker).
- Build Immutable Artifacts: Compile code or build Docker image exactly ONCE. Tag the artifact with the Git commit SHA.
- Promote the Artifact: Deploy the EXACT SAME artifact from Staging to Production. Do not rebuild for production.
- Monitor Deployment: Log deployment status, verify health checks, alert on failures.
- Rollback Strategy: Define clear rollback criteria and process (revert to previous artifact tag).
Rules
- MUST inject secrets/API keys via platform's secret manager (NEVER hardcode)
- MUST fail immediately if any step returns non-zero exit code
- MUST tag artifacts with commit SHA (no "latest" tag in production)
- MUST build artifact exactly once, then promote across environments
- MUST NOT rebuild code for different environments
- MUST NOT ignore flaky tests (use
continue-on-error: true) - MUST NOT allow manual deployments outside pipeline
- MUST cache dependencies between runs (optimization)
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.
- 5d ago First seen · 183 lines · 22 tokens per session scan A 81bb0d665d44
ci-cd-pipeline-architecture is a skill published in the GitHub repository KraitDev/skiLL.Md (7 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,733 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-31.
Other skills, from other repositories
monitor-ci
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI…
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
dyad:check-workflows
Check GitHub Actions workflow runs from the past day, identify severe or consistent failures, and file an issue if actionable problems are found.
dyad:pr-fix:ci
Diagnose and fix failing CI checks on a pull request from its latest GitHub Actions CI run. Use when PR CI has E2E/Playwright failures, macOS or Windows unit-test failures, or presubmit/type/build failures; analyzes the exact run logs and artifacts, invokes dyad:deflake-e2e-from-run for E2E failures, reproduces…
fix-ci
Investigate and fix the latest failing CI workflow.
sdlc
Show SDLC pipeline status dashboard.