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/amariahak/atlarix-skills/github-actionsnpx skills add AmariahAK/atlarix-skills --skill github-actionsgit clone --depth 1 https://github.com/AmariahAK/atlarix-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/amariahak/atlarix-skills/github-actions)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/github-actions"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-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.1 | $0.00005 | $0.00373 |
| Opus 5 | $0.00003 | $0.00187 |
| Sonnet 5 | $0.00001 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
GitHub Actions CI 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 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.
What it actually says
GitHub Actions CI Patterns
When to use this skill
Use this skill when adding or debugging GitHub Actions workflows and you want repeatable CI behavior, minimal permissions, and clear failure logs.
Core patterns
Keep workflows small and composable
Prefer:
- multiple jobs with clear responsibilities
- reusable workflows for shared logic
Permissions: least privilege
Set permissions: explicitly:
- default to read-only
- elevate only when needed (releases, writing checks)
Caching (only when it helps)
Cache:
- dependency directories (npm/pip/cargo)
Avoid caching build outputs unless you understand invalidation.
Deterministic installs
- use lockfiles
- use pinned tool versions where possible
Fail fast with good logs
- print tool versions
- print key environment info
- surface the failing command output
Local reproduction
When debugging:
- run the same commands locally
- match Node/Python versions from CI
Atlarix tool notes
- Explore: inspect
.github/workflows/*.ymland identify triggers and permissions. - Build: implement the minimal change; keep steps explicit.
- Review: check permissions and secrets handling.
Common mistakes to avoid
- Missing lockfiles leading to non-deterministic installs
- Overly broad permissions (
write-all) - Hidden failures due to
continue-on-error
Mini-checklist
- Permissions minimal
- Steps deterministic
- Logs useful
- Workflow names and job names clear
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.
- 2d ago First seen · 63 lines · 5 tokens per session scan A 0373cdb52a2d
GitHub Actions CI Patterns is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 5 tokens to every session and 373 once invoked, about $0.0000 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
github-actions
Operational skill for GitHub Actions CI/CD: workflows, jobs, matrices, caching, OIDC cloud auth, secrets, and reusable workflows.
workflow-setup
Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
GitHub CI Fix Debugging
Debug and fix failing GitHub PR checks by inspecting GitHub Actions logs, summarizing failure context, drafting fix plans, and implementing fixes after approval.
github-actions
Use when authoring or fixing GitHub Actions CI/CD — workflows under .github/workflows, triggers, job matrix, caching, token permissions, OIDC cloud deploys, environment gates, reusable workflows. NOT the Dockerfile or image build strategy (that is docker), NOT the branching model (that is git-workflow), NOT release…
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…