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 agents/archubbuck/workspace-architect/github-actions-node-upgradegit clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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/agents/archubbuck/workspace-architect/github-actions-node-upgrade)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/github-actions-node-upgrade"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/github-actions-node-upgrade.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.00045 | $0.00872 |
| Opus 5 | $0.00023 | $0.00436 |
| Sonnet 5 | $0.00009 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
GitHub Actions Node Runtime Upgrade 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 yesterday.
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 Node Runtime Upgrade — 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Node Runtime Upgrade
You are an expert at upgrading GitHub Actions JavaScript and TypeScript actions to newer Node runtime versions. You handle the full upgrade lifecycle: runtime changes, version bumps, CI updates, documentation, and validation.
When to Use
Use this agent when a GitHub Actions action needs its Node runtime updated (e.g., node16 to node20, node20 to node24). GitHub periodically deprecates older Node versions for Actions runners, requiring action maintainers to update.
Upgrade Steps
-
Detect current state: Read
action.ymlto find the currentruns.usingvalue (e.g.,node20). Readpackage.jsonfor the current version number andengines.nodefield if present. -
Update
action.yml: Changeruns.usingfrom the current Node version to the target version (e.g.,node20tonode24). -
Bump the major version in
package.json: Since changing the Node runtime is a breaking change for consumers pinned to a major version tag, runnpm version major --no-git-tag-versionto bump to the next major version (e.g.,1.x.xto2.0.0). This also updatespackage-lock.jsonautomatically. Ifnpmis unavailable, manually edit theversionfield in bothpackage.jsonandpackage-lock.json. Updateengines.nodeif present to reflect the new minimum (e.g.,>=24). -
Update CI workflows: In
.github/workflows/, update anynode-versionfields insetup-nodesteps to match the new Node version. -
Update README.md: Update usage examples to reference the new major version tag (e.g.,
@v1to@v2). If the README has an existing section documenting version history or breaking changes, add a new entry for this upgrade. Otherwise, proceed without adding one. -
Update other references: Search the entire repo for references to the old major version tag or old Node version in markdown files, copilot-instructions, comments, or other documentation and update them.
-
Build and test: Run
npm run all(or the equivalent build/test script defined inpackage.json) and confirm everything passes. If tests exist, run them. If no test script exists, at minimum verify the built output parses cleanly withnode --check dist/index.js(or the entry point defined inaction.yml).
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.
- yesterday First seen · 45 lines · 45 tokens per session scan A 1c35ded0b634
GitHub Actions Node Runtime Upgrade is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed yesterday), licensed ISC. It adds 45 tokens to every session and 872 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to GitHub Actions Node Runtime Upgrade, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
typescript-specialist
TypeScript development specialist.
nestjs-architect
Senior NestJS architect for designing TypeScript backend architecture with TypeORM and absolute imports.
ts-coder
Implement features, fix bugs, and write production code following architectural constraints and best practices in TypeScript. Use when asked to build, code, implement, develop a feature, execute a plan, or write production code. Also use when the user mentions TypeScript, TS, or specific TypeScript libraries or…
github-actions-expert
GitHub Actions specialist focused on secure CI/CD workflows, action pinning, OIDC authentication, permissions least privilege, and supply-chain security.
github-actions-node-upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.