Borrowing it
Nothing to install: this file belongs to RorroRojas3/awesome-claude-copilot. 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/RorroRojas3/awesome-claude-copilot/main/.claude/skills/github-actions-runtime-upgrade-conventions/SKILL.mdgit clone --depth 1 https://github.com/RorroRojas3/awesome-claude-copilotWrote 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/rorrorojas3/awesome-claude-copilot/github-actions-runtime-upgrade-conventions)<a href="https://agentmods.dev/skills/rorrorojas3/awesome-claude-copilot/github-actions-runtime-upgrade-conventions"><img src="https://agentmods.dev/badge/skills/rorrorojas3/awesome-claude-copilot/github-actions-runtime-upgrade-conventions/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/rorrorojas3/awesome-claude-copilot/github-actions-runtime-upgrade-conventions"><img src="https://agentmods.dev/badge/skills/rorrorojas3/awesome-claude-copilot/github-actions-runtime-upgrade-conventions.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.00033 | $0.00606 |
| Opus 5.5 | $0.00013 | $0.00242 |
| Sonnet 5.5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
github-actions-runtime-upgrade-conventions 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.
This is a copy
100% identical to github-actions-runtime-upgrade-conventions — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Runtime Upgrade Conventions
Use this skill when editing GitHub Actions workflows to address deprecation warnings about action runtimes (for example Node.js runtime migrations).
Use This Skill When
- Workflow logs report an action is running on a deprecated runtime.
- You are upgrading action versions in
.github/workflows/*.ymlor.github/workflows/*.yaml. - You need to keep existing workflow behavior while modernizing action dependencies.
Upgrade Rules
- Prefer upgrading to the latest stable major version of each action that is compatible with the workflow.
- Prefer immutable pins: resolve the target release to a full commit SHA and use that SHA in
uses:. - Do not pin to mutable tags or branches (for example
@v4or@main) in final recommendations. - Upgrade one action at a time per commit (or one tightly related group) so failures are easy to isolate.
- Keep existing workflow behavior unchanged while upgrading runtime/dependency actions.
Actions We Track in This Repo
Prioritize runtime review for these groups when warnings appear:
- Any first-party action under
actions/* - Especially setup actions under
actions/setup-*(for examplesetup-node,setup-python,setup-dotnet) - Any other action explicitly named by the runtime deprecation warning in workflow logs
Pinning Pattern
steps:
- uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608 # v4.3.1
- uses: actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8 # v4.0.4
When recommending upgrades, identify the latest compatible release first, then use the corresponding commit SHA with an optional version comment.
Verification Checklist
After changing action versions:
- Ensure all edited workflows still parse and keep the same triggers/permissions unless intentionally changed.
- Run the affected workflows (or equivalent local build/test commands) and confirm the upgraded steps complete successfully.
- Confirm release/signing/artifact steps still produce expected outputs where applicable.
- Check workflow run logs for any new deprecation warnings or runtime migration notes.
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 · 66 lines · 33 tokens per session scan A 1308b5fd16bc
github-actions-runtime-upgrade-conventions is a skill published in the GitHub repository RorroRojas3/awesome-claude-copilot (0 stars, last pushed 26d ago), licensed MIT. It adds 33 tokens to every session and 606 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to github-actions-runtime-upgrade-conventions, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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.
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.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
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.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…