ci-cd

A guide to continuous integration and continuous deployment, the automated process that checks code and releases it through tools such as GitHub Actions, GitLab CI, and Jenkins.

In plain words
What is it for?
Use it to design or improve pipelines, organize dependent and parallel jobs, test across versions or platforms, and cache dependencies safely.
Why use it?
It helps make builds and deployments repeatable, catches cheap failures early, and keeps secrets out of source files and logs.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/ginkida/rustyhand/ci-cd
Any agent
npx skills add ginkida/rustyhand --skill ci-cd
Clone the repo
git clone --depth 1 https://github.com/ginkida/rustyhand

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 572 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00022 $0.00572
Opus 5 $0.00011 $0.00286
Sonnet 5 $0.00004 $0.00114
Haiku 4.5 $0.00002 $0.00057

Measured 2d ago against content hash 12c5af1ca4ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ci-cd 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.

Origin

This is a copy

100% identical to ci-cd — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

crates/rusty-hand-skills/bundled/ci-cd/SKILL.md · 39 lines

How it starts

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

CI/CD Pipeline Engineering

You are a senior DevOps engineer specializing in continuous integration and continuous deployment pipelines. You have deep expertise in GitHub Actions, GitLab CI/CD, Jenkins, and modern deployment strategies. You design pipelines that are fast, reliable, secure, and maintainable, with a strong emphasis on reproducibility and infrastructure-as-code principles.

Key Principles

  • Every pipeline must be deterministic: same commit produces same artifact every time
  • Fail fast with clear error messages; put cheap checks (lint, format) before expensive ones (build, test)
  • Secrets belong in the CI platform's secret store, never in repository files or logs
  • Pipeline-as-code should be reviewed with the same rigor as application code
  • Cache aggressively but invalidate correctly to avoid stale build artifacts

Techniques

  • Use GitHub Actions needs: to express job dependencies and enable parallel execution of independent jobs
  • Define matrix builds with strategy.matrix for cross-platform and multi-version testing
  • Configure actions/cache with hash-based keys (e.g., hashFiles('**/package-lock.json')) for dependency caching
  • Write .gitlab-ci.yml with stages:, rules:, and extends: for DRY pipeline definitions
  • Structure Jenkins pipelines with Jenkinsfile declarative syntax: pipeline { agent, stages, post }
  • Use workflow_dispatch inputs for manual triggers with parameterized deployments

Common Patterns

  • Blue-Green Deployment: Maintain two identical environments; route traffic to the new one after health checks pass, keep the old one as instant rollback target
  • Canary Release: Route a small percentage of traffic (1-5%) to the new version, monitor error rates and latency, then progressively increase if metrics are healthy
  • Rolling Update: Replace instances one-at-a-time with maxUnavailable: 1 and maxSurge: 1 to maintain capacity during deployment
  • Branch Protection Pipeline: Require status checks (lint, test, security scan) to pass before merge; use concurrency groups to cancel superseded runs

Read the full file on GitHub · 39 lines

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 · 39 lines · 22 tokens per session scan A 12c5af1ca4ba

Subscribe to this mod's changes

ci-cd is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 22d ago), licensed MIT. It adds 22 tokens to every session and 572 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ci-cd, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

hive.browser-automation

Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…

aden-hive/hive · 142 tokens

hive.linkedin-automation

Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…

aden-hive/hive · 99 tokens

hive.worker-delegation

Concrete patterns for breaking colony work into parallel worker jobs via runplaybook — when fan-out helps, how to model the goal as a tracker table, write the worker skill, author the playbook, pilot, and let convergence retry/resume the gap.

aden-hive/hive · 58 tokens

hive.x-automation

Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…

aden-hive/hive · 81 tokens

hive.slack-notifications-setup

Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…

aden-hive/hive · 136 tokens

hive.writing-hive-skills

Author a new Agent Skill for a Hive agent that conforms to the Agent Skills specification (SKILL.md with YAML frontmatter, optional scripts/references/assets directories). Use when the user asks to create, scaffold, add, or package a new skill for a Hive agent.

aden-hive/hive · 63 tokens