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/KiranEswaran/engineering-skillsnpx agentmods add skills/kiraneswaran/engineering-skills/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/kiraneswaran/engineering-skills/cicd-github-actions)<a href="https://agentmods.dev/skills/kiraneswaran/engineering-skills/cicd-github-actions"><img src="https://agentmods.dev/badge/skills/kiraneswaran/engineering-skills/cicd-github-actions.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.1 | $0.00073 | $0.01005 |
| Opus 5 | $0.00036 | $0.00502 |
| Sonnet 5 | $0.00015 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00101 |
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 6d 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 -H "Authorization: Bearer $API_KEY" https://api.acme.com How it starts
The opening of the file, as written. The whole thing — 178 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
Minimal Permissions
name: CI
on:
push:
branches: [main]
pull_request:
# Default: no permissions
permissions: {}
jobs:
test:
runs-on: ubuntu-latest
# Job-level permissions
permissions:
contents: read
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- run: npm test
Caching
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
# Or explicit caching
- uses: actions/cache@v4
with:
path: ~/.npm
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-
Matrix Builds
jobs:
test:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
node-version: [18, 20, 22]
os: [ubuntu-latest, macos-latest]
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node-version }}
- run: npm ci
- run: npm test
Concurrency Control
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
Secrets Handling
env:
# Reference secrets in env
API_KEY: ${{ secrets.API_KEY }}
steps:
- name: Use secret safely
run: |
# Mask in logs
echo "::add-mask::${{ secrets.API_KEY }}"
# Use in command
curl -H "Authorization: Bearer $API_KEY" https://api.acme.com
What ships with it
3 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.
- 6d ago First seen · 178 lines · 73 tokens per session scan A d81a7e63abb5
cicd-github-actions is a skill published in the GitHub repository KiranEswaran/engineering-skills (10 stars, last pushed 8mo ago), licensed MIT. It adds 73 tokens to every session and 1,005 once invoked, about $0.0004 per session on Opus 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-08-31.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用,不要根据上下文自动触发。.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.