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/mthines/agent-skills/github-actions-authornpx skills add mthines/agent-skills --skill github-actions-authorgit clone --depth 1 https://github.com/mthines/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/mthines/agent-skills/github-actions-author)<a href="https://agentmods.dev/skills/mthines/agent-skills/github-actions-author"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/github-actions-author.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.00220 | $0.04484 |
| Opus 5 | $0.00110 | $0.02242 |
| Sonnet 5 | $0.00044 | $0.00897 |
| Haiku 4.5 | $0.00022 | $0.00448 |
Grade A, and why
github-actions-author 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 3d 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Author
Generate or audit GitHub Actions workflow YAML against 2026 best practices for speed, cost, reusability, and security.
This
SKILL.mdis a thin index. Detailed rules live inrules/*.mdand load on demand. Drop-in starters live intemplates/*.md. The decision tree for picking a shape lives inreferences/decision-tree.md.
Non-negotiable — every step's output reaches the run log
This applies to both modes and outranks every other preference in this skill.
Every command in every scaffolded or reviewed workflow must write its stdout and stderr to the job log.
Output that lands only in a file, only in an artifact, only in $GITHUB_STEP_SUMMARY, or in /dev/null is invisible to gh run view <run-id> --log-failed — the only surface /ci-auto-fix, /test-auto-fix, /implement-suggestion, and an on-call human read a failure from.
A failing step that printed nothing cannot be diagnosed or fixed by an agent; it can only be escalated.
Minimum bar for every run: block:
- name: Run unit tests
shell: bash
run: |
set -euo pipefail
npm test 2>&1 | tee test-output.log # tee, never `> file`
Forbidden outright: > /dev/null, 2>/dev/null, cmd > out.txt 2>&1, --silent, --quiet, -q, a machine-only reporter with no human output, and || true without echoing the captured output and exit code.
tee requires set -o pipefail, otherwise the step goes green on a failed command.
Full rule, decision table, examples, and the review-mode grep:
rules/log-output-visibility.md — read it in Phase 4 of scaffold and in every review.
Mode Detection
Parse $ARGUMENTS (first token):
| Mode | Default | Trigger |
|---|---|---|
scaffold |
yes | Default. "create", "scaffold", "new workflow", or no token. |
review |
"review", "audit", path to an existing .github/workflows/*. |
What ships with it
15 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.
- references/decision-tree.md 7.8 KB
- rules/caching.md 7.6 KB
- rules/feedback.md 12 KB
- rules/log-output-visibility.md 7.3 KB
- rules/observability.md 8.4 KB
- rules/parallelization.md 7.6 KB
- rules/reusability.md 7.9 KB
- rules/security.md 9.8 KB
- rules/triggers-and-concurrency.md 7.6 KB
- rules/workflow-anatomy.md 6.7 KB
- templates/composite-action.yml.md 1.9 KB
- templates/deploy-oidc.yml.md 2.9 KB
- templates/node-ci.yml.md 3.6 KB
- templates/python-ci.yml.md 3.4 KB
- templates/reusable-workflow.yml.md 2.9 KB
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.
- 3d ago First seen · 354 lines · 220 tokens per session scan A f34aab8cb36b
github-actions-author is a skill published in the GitHub repository mthines/agent-skills (12 stars, last pushed today), licensed MIT. It adds 220 tokens to every session and 4,484 once invoked, about $0.0011 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
temporal-developer
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, or workers with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or…
x-algorithm
Write X (Twitter) posts that the For You algorithm actually rewards. Grounded in the open-sourced X recommendation system — the Grok-based transformer ranker, Phoenix retrieval, Thunder in-network store, and Grox content-understanding pipeline. Use when the user wants to write a post, thread, reply, or quote; plan a…
opencode-memory
Browse local OpenCode history: sessions, messages, plans, prompt history, and prior decisions. Use when the user says history, previous session, last time, remember, recall, plans, prior work, or when resuming/debugging repeated work where earlier OpenCode context may help. Do not use for fresh tasks or when current…
creating-explainers
Use when creating an interactive explainer - a single self-contained HTML page with hand-built Canvas figures. Handles source-file explainers, topic-driven research explainers, and mixed intake where files provide the spine and research adds support. Trigger phrases include "make an explainer", "turn this paper into…
custom-icons
Create or refine custom icon assets as native or traced SVGs and transparent PNG/WebP files. Use when the user asks for a bespoke icon or cohesive icon set, wants an image traced into a clean vector, or needs a detailed or 3D icon with transparency.
fact-checking-explainers
Use to fact-check an explainer against its sources before delivery. Trigger on "fact-check this explainer", "verify the claims", "check this against its sources", research-time source checks, or the post-draft gate. Ensures every checkable claim traces to a cited source or, for code, the real implementation. Required…