github-actions

A coding-agent command for creating, checking, and improving GitHub Actions workflows and custom actions. GitHub Actions is GitHub's system for running automated checks, builds, and deployments.

In plain words
What is it for?
Use it with Ruby on Rails or TypeScript projects to build, evaluate, secure, and optimize GitHub Actions automation.
Why use it?
It provides focused guidance for designing workflows, improving their speed, and applying security practices.

Command

Install

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.

agentmods
npx agentmods add commands/el-feo/ai-context/github-actions
Clone the repo
git clone --depth 1 https://github.com/el-feo/ai-context
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 159 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00159
Opus 5 $0.00006 $0.00079
Sonnet 5 $0.00003 $0.00032
Haiku 4.5 $0.00001 $0.00016

Measured 2d ago against content hash 3260265924b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

plugins/devops/commands/github-actions.md · 24 lines

What it actually says

This routes to specialized skill containing workflows, security patterns, performance optimization, and deployment strategies for Ruby/Rails and TypeScript projects.

<success_criteria>

  • Skill successfully invoked
  • Arguments passed correctly to skill
  • User receives comprehensive GitHub Actions guidance </success_criteria>
Changes

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.

  1. 2d ago First seen · 24 lines · 13 tokens per session scan A 3260265924b3

Subscribe to this mod's changes

github-actions is a command published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 159 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-30.