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/mujez/claude-skills/github-actionsnpx skills add mujez/claude-skills --skill github-actionsgit clone --depth 1 https://github.com/mujez/claude-skillsWrote 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/mujez/claude-skills/github-actions)<a href="https://agentmods.dev/skills/mujez/claude-skills/github-actions"><img src="https://agentmods.dev/badge/skills/mujez/claude-skills/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 | $0.00056 | $0.02311 |
| Opus 5 | $0.00028 | $0.01156 |
| Sonnet 5 | $0.00011 | $0.00462 |
| Haiku 4.5 | $0.00006 | $0.00231 |
Grade A, and why
github-actions 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 4d 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are operating as a Principal DevOps Engineer with 10+ years of CI/CD experience, specializing in GitHub Actions pipelines for production workloads.
Pipeline Design Principles
Fail fast → Parallelize → Cache → Build once → Deploy many
1. Fast feedback (lint, format) → <1 min
2. Unit tests → 1-5 min
3. Security scanning (SAST, SCA) → 2-5 min
4. Integration tests → 5-15 min
5. Build artifacts → 2-5 min
6. E2E tests (main branch only) → 15-30 min
7. Deploy (with approval gates) → 2-10 min
Workflow Structure
name: CI/CD
on:
push:
branches: [main]
pull_request:
branches: [main]
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- # lint steps
test:
runs-on: ubuntu-latest
needs: [lint]
strategy:
matrix:
shard: [1, 2, 3]
steps:
- uses: actions/checkout@v4
- # test steps with sharding
build:
runs-on: ubuntu-latest
needs: [test]
steps:
- uses: actions/checkout@v4
- # build and upload artifact
deploy:
runs-on: ubuntu-latest
needs: [build]
if: github.ref == 'refs/heads/main'
environment:
name: production
url: https://example.com
steps:
- # download artifact and deploy
Caching Strategies
Node.js
- uses: actions/setup-node@v4
with:
node-version: '22'
cache: 'npm'
- run: npm ci
Go
- uses: actions/setup-go@v5
with:
go-version: '1.23'
cache: true
- run: go build ./...
Docker Layer Caching
- uses: docker/build-push-action@v6
with:
context: .
cache-from: type=gha
cache-to: type=gha,mode=max
Custom Cache
- uses: actions/cache@v4
with:
path: |
~/.cache/custom
./build-cache
key: ${{ runner.os }}-custom-${{ hashFiles('**/lockfile') }}
restore-keys: |
${{ runner.os }}-custom-
What ships with it
1 file 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.
- 4d ago First seen · 390 lines · 56 tokens per session scan A 5e888772ce95
github-actions is a skill published in the GitHub repository mujez/claude-skills (47 stars, last pushed 6mo ago), licensed MIT. It adds 56 tokens to every session and 2,311 once invoked, about $0.0003 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
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
upgrading-golang
Upgrades Go version across the entire Chainloop codebase including source files, Docker images, CI/CD workflows, and documentation. Use when the user mentions upgrading Go, golang version, or updating Go compiler version.
python-canary-fix
Investigate and propose fixes for Python canary cron failures in the openinference repo. Use when the user mentions Python canary failures, Python cron failures, or when the auto-fix CI job reports Python instrumentation canary issues.
ci-fixer
CI failures - read error, minimal fix, verify.
infrastructure-setup
Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Use when: "настрой инфраструктуру", "измени CI/CD", "подготовь деплой", "настрой Docker", "собери release artifact", "настрой мониторинг"…