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 skills add G1Joshi/Agent-Skills --skill github-actionsgit clone --depth 1 https://github.com/G1Joshi/Agent-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/g1joshi/agent-skills/github-actions)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/github-actions"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-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.00019 | $0.00489 |
| Opus 5 | $0.00010 | $0.00244 |
| Sonnet 5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
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.
What it actually says
GitHub Actions
GitHub Actions is the CI/CD platform native to GitHub. In 2025, it is the dominant CI/CD tool, characterized by Reusable Workflows and OIDC integration for passwordless deployments.
When to Use
- GitHub-Hosted: Your code is already on GitHub. Deep integration with Issues/PRs.
- Simplicity: No servers to manage (unlike Jenkins).
- Marketplace: Thousands of pre-built actions (setup-node, docker-build-push).
Quick Start
# .github/workflows/ci.yml
name: CI
on: [push, pull_request]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: "20"
- run: npm ci
- run: npm test
Core Concepts
Workflows
Defined in .github/workflows/*.yml. Triggered by events (push, release, schedule).
Runners
Virtual machines (Ubuntu/Windows/MacOS) that run your jobs. You can also host Self-Hosted Runners for cheaper/faster builds in your VPC.
Actions
Reusable steps. actions/checkout is an action. You can write your own in JS or Docker.
Best Practices (2025)
Do:
- Use Reusable Workflows: Define a standard "Deploy to Prod" workflow in one repo, and call it from 50 microservices.
- Use OIDC: Authenticate to AWS/Azure/GCP using
permissions: id-token: writeinstead of long-lived secrets. - Pin Actions: Use
actions/checkout@v4or a specific SHA for immutability.
Don't:
- Don't hardcode secrets: Use Repository Secrets or Environment Secrets.
- Don't write huge shell scripts: If a step is >10 lines of bash, move it to a script file or a custom Action.
References
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 · 65 lines · 19 tokens per session scan A df9ced53106a
github-actions is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 489 once invoked, about $0.0001 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
ci-cd-pipelines
When designing GitHub Actions workflows, optimizing pipeline speed, implementing deployment gates.
general-dev-tools
Core development tools used across any project — git, docker, make, CI/CD, linting, formatting, pre-commit hooks.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
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.
conductor-revert
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.