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/roedyrustam/vibes-plug/ci-cd-devops-architectnpx skills add roedyrustam/vibes-plug --skill ci-cd-devops-architectgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/ci-cd-devops-architect)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/ci-cd-devops-architect"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/ci-cd-devops-architect.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.00040 | $0.01224 |
| Opus 5 | $0.00020 | $0.00612 |
| Sonnet 5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
ci-cd-devops-architect 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD & DevOps Architect / Arsitek CI/CD & DevOps
English
Description
Design and maintain CI/CD pipelines (GitHub Actions, GitLab CI, Buildkite) and manage infrastructure using Docker, Kubernetes (1.30+), and Terraform/OpenTofu.
Orchestration & Integration
Connect with these skills to orchestrate complete workflows:
cloud-hosting-expert— Deployment targets (Vercel, Cloudflare, AWS, Railway)dependency-upgrade-migrator— Renovate Bot configuration in CI/CDself-healing-cloud-orchestrator— Auto-remediation and rollback pipelineslogging-error-tracking-expert— Sentry source map upload step in build pipelinee2e-testing-expert— Automated Playwright & Vitest test steps in CIzero-trust-secret-vault— CI/CD secret management and injectionproduction-ready-hardener— Pre-deployment security scanning in CI
Key CI/CD Workflows & Patterns
- Automate Everything: Enforce tests, linting, formatting, and security scans on every PR. Block merges on pipeline failure.
- Dependency Update Bot: Configure Renovate Bot for automated patch/minor updates (
dependency-upgrade-migrator). - Source Maps Upload: Upload Sentry source maps during build phase (
logging-error-tracking-expert). - Immutable Artifacts: Build Docker image once, deploy identical image to Staging and Production. Inject environment variables dynamically at runtime.
- Infrastructure as Code: Store all infrastructure configurations (Terraform/OpenTofu, K8s manifests) in version control. No manual web console changes.
- Zero-Trust Secrets: Never commit secrets. Use Infisical, GitHub OIDC, or HashiCorp Vault (
zero-trust-secret-vault). - Zero-Downtime Deployments: Utilize rolling updates or blue-green deployments.
Implementation Checklist
- Configure branch protection (require passing status checks before merge).
- Set up multi-stage Docker builds to reduce image size and attack surface.
- Implement caching for package managers (pnpm, bun, cargo, go mod) in CI.
- Scan container images for vulnerabilities before registry push.
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 · 82 lines · 40 tokens per session scan A 6dc39bc7ebb4
ci-cd-devops-architect is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,224 once invoked, about $0.0002 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-30.
Other skills, from other repositories
devops
World-class DevOps engineering - cloud architecture, CI/CD pipelines, infrastructure as code, and the battle scars from keeping production running at 3amUse when "devops, infrastructure, deployment, ci/cd, docker, kubernetes, aws, gcp, azure, terraform, cloudflare, vercel, monitoring, alerting, pipeline, container…
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
dep
Handles containerization, CI/CD pipelines, and deployment setup.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
mlops-automation
Automate an MLOps project with mise tasks, lefthook hooks, Docker images, GitHub Actions, and MLflow tracking on a SQL backend. Use when adding a task runner, git hooks, CI/CD, or experiment tracking to a working package.