Borrowing it
Nothing to install: this file belongs to richardwooding/feed-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/richardwooding/feed-mcp/main/.claude/skills/gh-actions-node24-migration/SKILL.mdgit clone --depth 1 https://github.com/richardwooding/feed-mcpWrote 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/richardwooding/feed-mcp/gh-actions-node24-migration)<a href="https://agentmods.dev/skills/richardwooding/feed-mcp/gh-actions-node24-migration"><img src="https://agentmods.dev/badge/skills/richardwooding/feed-mcp/gh-actions-node24-migration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/richardwooding/feed-mcp/gh-actions-node24-migration"><img src="https://agentmods.dev/badge/skills/richardwooding/feed-mcp/gh-actions-node24-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.01475 |
| Opus 5 | $0.00000 | $0.00737 |
| Sonnet 5 | $0.00000 | $0.00295 |
| Haiku 4.5 | $0.00000 | $0.00147 |
Grade A, and why
gh-actions-node24-migration 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gh-actions-node24-migration — 89% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Node 24 Migration
GitHub is retiring the Node 20 runtime on Actions runners. The runner default flips from Node 20 to Node 24, then Node 20 is removed entirely. Two audiences must act:
- Workflow authors — bump
uses:references to action versions whose publishedaction.ymldeclares Node 24. - Action authors — change
runs.using: node20tonode24in their action's metadata file.
This skill drives that migration deterministically: a single audit script classifies every action reference in a repo, and an apply script rewrites the safe ones in place.
Quick start
# 1. Audit (read-only). Writes audit.json next to the cwd and prints a markdown table.
python scripts/audit.py <repo-root>
# 2. Review the table. Decide which findings to take.
# 3. Dry-run the rewrite (default — prints unified diffs, writes nothing).
python scripts/apply_fix.py audit.json
# 4. Apply for real once the diffs look right.
python scripts/apply_fix.py audit.json --apply
gh (GitHub CLI) must be installed and authenticated — the audit calls gh api to read each action's action.yml at its pinned ref and to discover the latest Node 24 release.
What gets audited
**/.github/workflows/*.ymland*.yaml— everyuses:line (job steps and reusable workflows).- Top-level
action.yml/action.yamland any nested**/action.yml— theruns.usingfield. - Composite actions — recursed into
runs.steps[].uses.
Actions are classified into one of these states:
| State | Meaning | Auto-fixable |
|---|---|---|
node24 |
Already on Node 24. | — |
node20-fixable |
On Node 20; a Node 24 release exists upstream. | yes |
node20-stuck |
On Node 20; no Node 24 release published yet. | no — flag only |
local-node20 |
Local action.yml declares runs.using: node20. |
yes (rewrite) |
composite |
Composite action — judged by its inner uses: references. |
recursed |
docker |
Docker-based action; not affected by the Node deprecation. | skip |
unresolved |
action.yml not reachable (private, archived, deleted). |
no — flag only |
What ships with it
5 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.
- 9d ago First seen · 79 lines · 0 tokens per session scan A 025da68ca6b9
gh-actions-node24-migration is a skill published in the GitHub repository richardwooding/feed-mcp (34 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,475 tokens. 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.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
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.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.