Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbooknpx agentmods add skills/d-padmanabhan/agent-engineering-handbook/cicd-github-actionsWrote 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/d-padmanabhan/agent-engineering-handbook/cicd-github-actions)<a href="https://agentmods.dev/skills/d-padmanabhan/agent-engineering-handbook/cicd-github-actions"><img src="https://agentmods.dev/badge/skills/d-padmanabhan/agent-engineering-handbook/cicd-github-actions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/d-padmanabhan/agent-engineering-handbook/cicd-github-actions"><img src="https://agentmods.dev/badge/skills/d-padmanabhan/agent-engineering-handbook/cicd-github-actions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00073 | $0.02118 |
| Opus 5.5 | $0.00029 | $0.00847 |
| Sonnet 5.5 | $0.00015 | $0.00424 |
| Haiku 4.5 | $0.00007 | $0.00212 |
Grade A, and why
cicd-github-actions scanned grade A with 1 finding 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 21d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --fail --silent --show-error \ How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions CI/CD
Core Objectives
- Security: Minimal permissions, secrets handling, OIDC
- Performance: Caching, matrix builds, parallelization
- Maintainability: Reusable workflows, composite actions
- Reliability: Concurrency control, retry logic
Essential Checklist
- Workflows use minimal permissions (
permissions: {}at root) - Secrets never logged or exposed in artifacts
- Concurrency control configured
- Timeout values set on all jobs
- Caching implemented for dependencies
- PR workflows use
pull_request, notpull_request_target - A bordered operational header follows the workflow
name: - Untrusted contexts and inputs reach shell commands through step-level
env - Production deploys use protected GitHub Environments
- Changed workflows pass
actionlint
Workflow Authoring Contract
Put a bordered operational comment block immediately after the workflow name.
Use the headings Purpose, Triggers, Required Secrets, and Dependencies,
with blank comment lines between sections. Record approval, rollback, recovery,
or runbook requirements under Dependencies.
name: Deploy Application
# ================================================================
# Purpose: Deploys a tested release to a protected environment
#
# Triggers:
# - Manual workflow dispatch
#
# Required Secrets:
# - None: cloud authentication uses OIDC
#
# Dependencies:
# - Published release artifact
# - Production GitHub Environment approval
# - Rollback runbook: docs/deployment-rollback.md
# ================================================================
Document reusable workflow and action inputs, outputs, secrets, defaults, and side effects where they are declared. Give jobs and non-obvious steps descriptive names, but do not add comments that merely restate YAML. Keep secret values, sensitive identifiers, and production data out of comments, summaries, logs, and artifacts.
Use the workflow documentation reference for the complete header pattern, interface descriptions, comments, summaries, and review checklist.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 21d ago Changed · +64 lines 397553760db1
- 26d ago Changed · +8 lines d8d2daa6421b
- 1mo ago Changed · -4 lines 7e679550f666
- 1mo ago First seen · 224 lines · 73 tokens per session scan A 506273bc6d01
cicd-github-actions is a skill published in the GitHub repository d-padmanabhan/agent-engineering-handbook (19 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 2,118 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…