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 fabioc-aloha/Alex_Skill_Mall --skill github-actions-version-upgradesgit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/github-actions-version-upgrades)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/github-actions-version-upgrades"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/github-actions-version-upgrades/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/fabioc-aloha/alex_skill_mall/github-actions-version-upgrades"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/github-actions-version-upgrades.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00544 |
| Opus 5.5 | $0.00007 | $0.00218 |
| Sonnet 5.5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
github-actions-version-upgrades 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 1mo 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 Version Upgrades
The Problem
Older action versions trigger deprecation warnings and will eventually break:
# Deprecated - old action majors and pre-24 Node runners
- uses: actions/checkout@vOLD
- uses: actions/setup-node@vOLD
with:
node-version: '<24'
The Solution
Proactively use current versions:
# Current ACT baseline
- uses: actions/checkout@v6
- uses: actions/setup-node@v6
with:
node-version: '24'
Version Reference
| Action | Current | Node.js Runtime |
|---|---|---|
| actions/checkout | v6 | Node 24 |
| actions/setup-node | v6 | Node 24 |
| actions/upload-artifact | latest Node 24-compatible major | Node 24 |
| actions/download-artifact | latest Node 24-compatible major | Node 24 |
| actions/cache | latest Node 24-compatible major | Node 24 |
| actions/github-script | latest Node 24-compatible major | Node 24 |
Migration Script
# Update core actions to the Node 24-compatible majors
sed -i 's/actions\/checkout@v[0-5]/actions\/checkout@v6/g' .github/workflows/*.yml
sed -i 's/actions\/setup-node@v[0-5]/actions\/setup-node@v6/g' .github/workflows/*.yml
sed -i 's/actions\/upload-artifact@v[0-3]/actions\/upload-artifact@v4/g' .github/workflows/*.yml
sed -i 's/actions\/download-artifact@v[0-3]/actions\/download-artifact@v4/g' .github/workflows/*.yml
Node.js Version Matrix
strategy:
matrix:
node-version: ['24']
# ACT baseline
node-version: '24'
Verification
# Check for old versions
grep -rn 'actions/.*@v[0-3]' .github/workflows/
# Should return nothing after upgrade
When to Apply
- New repository setup
- Quarterly maintenance
- When seeing deprecation warnings
- Before Node.js version EOL dates
Tags
github-actions ci-cd maintenance node
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.
- 1mo ago First seen · 84 lines · 18 tokens per session scan A d349864943f9
github-actions-version-upgrades is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (5 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 544 once invoked, about $0.0001 per session on Opus 5.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
ai-agents-portability-campaign
Execute cross-harness hook changes for Claude Code and GitHub Copilot CLI using the settled official contract, versioned probes, generators, and runtime tests. Use for run the portability campaign, port hooks to a new harness, copilot hook timeout regression, or new copilot cli release, recheck the contract. Do NOT…
memory-enhancement
Manage memory citations, verify code references, and track confidence scores. Use when adding citations to memories, checking memory health, or verifying code references are still valid. Use when you say "add a citation", "verify this memory's code refs", "check memory health". Do NOT use for searching or creating…
panning-for-gold
Triage raw unstructured input (transcripts, brain dumps) into evaluated thread inventories and a synthesized gold-found file. Four phases: front-gate, extract, evaluate, synthesize. Use when you say "pan for gold", "triage transcript", "synthesize gold-found", or hand it a voice transcript or brain dump. Do NOT use…
pre-mortem
Guide prospective hindsight analysis to identify project risks before failure occurs. Teams imagine the project has failed spectacularly, then work backward to identify causes. Increases risk identification by 30% compared to traditional planning. Use when you say "run a pre-mortem on", "what could cause this to…
prompt-engineer
Optimize system prompts for Claude Code agents using proven prompt engineering patterns. Use when users request prompt improvement, optimization, or refinement for agent workflows, tool instructions, or system behaviors. Use when you say "optimize this prompt", "improve this system prompt", or "review my agent prompt".
serena-code-architecture
Architectural analysis workflow using Serena symbols and Forgetful memory. Use when you say "analyze the architecture of this project", "map out the codebase structure", "trace dependencies for this component", "document the architecture", or "what components does this project have". Do NOT use to populate the…