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/pledgeandgrow/pledge-skills/github-actionsnpx skills add pledgeandgrow/pledge-skills --skill github-actionsgit clone --depth 1 https://github.com/pledgeandgrow/pledge-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/pledgeandgrow/pledge-skills/github-actions)<a href="https://agentmods.dev/skills/pledgeandgrow/pledge-skills/github-actions"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-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.00028 | $0.02185 |
| Opus 5 | $0.00014 | $0.01092 |
| Sonnet 5 | $0.00006 | $0.00437 |
| Haiku 4.5 | $0.00003 | $0.00218 |
Grade A, and why
github-actions-docs 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions
Version: Latest (2026) | Source: docs.github.com/en/actions
Overview
GitHub Actions is a CI/CD platform that automates build, test, and deployment pipelines directly from your repository. Workflows are defined as YAML files in .github/workflows/ and triggered by repository events, schedules, or manual dispatch.
Quick Reference
| Topic | File | Key Content |
|---|---|---|
| Getting Started | getting-started.md |
Understanding Actions, quickstart, workflow templates, triggers, runners selection, workflow tasks |
| Workflow Syntax | workflow-syntax.md |
Full YAML syntax: name, on, jobs, steps, strategy, matrix, container, services, concurrency, permissions, env, defaults, reusable jobs, filter patterns |
| Events, Contexts & Expressions | events-contexts.md |
All 30+ trigger events, 12 contexts (github, env, vars, job, jobs, steps, runner, secrets, strategy, matrix, needs, inputs), expression operators, functions, status checks |
| Runners | runners.md |
GitHub-hosted runners (Ubuntu/Windows/macOS), larger runners, self-hosted runners, Actions Runner Controller (ARC) |
| Security & Reuse | security-reuse.md |
Secrets management, OIDC, artifact attestations, GITHUB_TOKEN permissions, custom actions (JS/composite/Docker), metadata syntax, reusable workflows |
| Managing Workflows | managing.md |
Manual runs, re-running, canceling, disabling, status badges, auto-labeling issues, scripts, deployment to Azure/AWS/GKE, limits, metrics |
| Caching, Artifacts, Variables & Commands | caching-commands.md |
Dependency caching (actions/cache, keys, restore-keys), artifacts (upload/download), default environment variables (GITHUB_, RUNNER_), config variable precedence, workflow commands (debug, notice, warning, error, group, mask, GITHUB_ENV, GITHUB_OUTPUT, GITHUB_PATH, GITHUB_STEP_SUMMARY) |
| Advanced Topics | advanced.md |
Deployment environments (protection rules, required reviewers, wait timer, branch restrictions, env secrets/vars), debug logging (runner diagnostic, step debug), billing & usage (minute multipliers, included minutes, storage), GITHUB_TOKEN authentication (API calls, CLI, permissions), REST API (workflows, runs, artifacts, caches, secrets, runners), migration from Jenkins/CircleCI/GitLab/Azure Pipelines (concept mapping tables), service containers (PostgreSQL, Redis) |
What ships with it
8 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.
- 4d ago First seen · 164 lines · 28 tokens per session scan A 3964f4db3254
github-actions-docs is a skill published in the GitHub repository pledgeandgrow/pledge-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 2,185 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-08-31.
Other skills, from other repositories
github-actions-ci
Structure GitHub Actions workflows — jobs, steps, caching, matrix builds, secrets, and a quality gate that blocks merges.
devops-cicd
CI/CD pipelines, infrastructure as code, and deployment strategies.
ci-status-checker
Interprets GitHub Actions run status and logs, diagnoses CI failure patterns, and suggests targeted fixes. Handles dependency install failures, test timeouts, build OOM, flaky tests, and workflow misconfigurations. Activate on: 'CI failing', 'build broken', 'workflow error', 'GitHub Actions debug', 'flaky CI'…
ci-sentinel
Daily autonomous classifier for failing PRs across your repos. Runs /ci-debug headless against every open PR with red required checks, posts the verdict as a collapsed PR comment, and appends to a per-repo .sentinel/ledger.jsonl. v1 is propose-don't-apply — NEVER auto-pushes a fix. Use when you're tired of /status…
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…
Artillery Load Testing
Write and run Artillery load tests with YAML phases and scenarios, CSV data payloads, the expect plugin for functional checks, and ensure thresholds that fail CI when latency or error budgets are breached.