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/ihatesea69/kiro-kit/ci-cd-patternsnpx skills add ihatesea69/kiro-kit --skill ci-cd-patternsgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/ci-cd-patterns)<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/ci-cd-patterns"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/ci-cd-patterns.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.00033 | $0.00314 |
| Opus 5 | $0.00016 | $0.00157 |
| Sonnet 5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
ci-cd-patterns 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 yesterday.
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.
What it actually says
CI/CD Patterns
Activate this skill when designing or optimizing CI/CD pipelines.
When to Use
- Designing new CI/CD pipelines
- Optimizing build times and caching
- Implementing deployment strategies
- Adding security scanning to pipelines
- Setting up multi-environment promotion
- Configuring GitOps workflows
Pipeline Stages
- Validate: lint, format check, schema validation
- Build: compile, bundle, create artifacts
- Test: unit, integration, contract tests
- Scan: SAST, dependency audit, container scan
- Package: build container image, push to registry
- Deploy: apply to target environment
- Verify: smoke tests, health checks, canary analysis
Deployment Strategies
- Rolling: gradual replacement, zero-downtime
- Blue-Green: instant switch between environments
- Canary: route percentage of traffic to new version
- Feature Flags: deploy dark, enable incrementally
Rules
- Fail fast: cheapest checks run first
- Cache aggressively: dependencies, layers, build artifacts
- Pin versions: actions, base images, dependencies
- Use OIDC: no long-lived credentials in CI
- Separate build from deploy for auditability
- Every deployment must be reversible
- Quality gates must block on failure
- Pipeline changes require code review
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.
- yesterday First seen · 46 lines · 33 tokens per session scan A cf639a11c8eb
ci-cd-patterns is a skill published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 16d ago), licensed MIT. It adds 33 tokens to every session and 314 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-09-03.
Other skills, from other repositories
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
ecs-devops
Use when someone is deploying, releasing, or shipping software to Amazon ECS — phrased as "blue/green deployment on ECS", "canary deployment for my ECS service", "set up CI/CD for ECS", "GitHub Actions deploy to Fargate", "my ECS deployment is stuck", "ECS deployment circuit breaker", "ECS task sets", or "migrate off…
argo-cd
Use this skill when designing GitOps delivery workflows with Argo CD. This covers Application and AppProject CRDs, the App of Apps pattern, sync policies and waves, health checks, RBAC configuration, and integrating Argo CD into a multi-environment or multi-cluster strategy. The AI will act as a GitOps specialist who…
gitlab-ci
Use this skill when designing or debugging GitLab CI/CD pipelines. This covers .gitlab-ci.yml configuration, GitLab Runners, pipeline stages, DAG (Directed Acyclic Graph) pipelines, merge request pipelines, include/extends patterns, and environment-based deployments. The AI will act as a specialist in GitLab CI idioms…
jenkins
Use this skill when designing or debugging Jenkins pipelines. This covers Declarative Jenkinsfile syntax, shared libraries, agent configuration, parallel stages, credentials binding, and integrating Jenkins into a broader CI/CD ecosystem. The AI will act as a Jenkins specialist who knows the difference between…
terraform-skill
Use when writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops - diagnoses failure mode (identity churn, secrets, blast radius, CI drift, state corruption) with version-aware guards.