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 yu-iskw/coding-agent-fabric --skill node-upgradegit clone --depth 1 https://github.com/yu-iskw/coding-agent-fabricWrote 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/yu-iskw/coding-agent-fabric/node-upgrade)<a href="https://agentmods.dev/skills/yu-iskw/coding-agent-fabric/node-upgrade"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/node-upgrade/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/yu-iskw/coding-agent-fabric/node-upgrade"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/node-upgrade.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.00039 | $0.00615 |
| Opus 5.5 | $0.00016 | $0.00246 |
| Sonnet 5.5 | $0.00008 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
node-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 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 node-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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Safe Node.js Dependency Upgrade
This skill provides a structured process for safely upgrading Node.js dependencies, ensuring project stability through pre-upgrade health checks and post-upgrade validation.
1. Preparation & Health Check
Before making any changes, verify the current state of the project:
- Baseline Health Check:
- Run an audit:
pnpm audit. - Run the test suite:
pnpm test. - Constraint: If the baseline tests fail, resolve those issues before proceeding with upgrades.
- Run an audit:
- Backup:
- Backup
package.jsonand the lockfile:cp pnpm-lock.yaml pnpm-lock.yaml.bak.
- Backup
2. Upgrade Execution
Choose the appropriate upgrade path based on the user's request. Refer to ../common-references/pnpm-commands.md for pnpm-specific commands.
Targeted Upgrade (Recommended)
Use this when the user specifies a package or a small set of packages.
- Upgrade: Run the targeted upgrade command (e.g.,
pnpm update <package>). - Verify: Check
package.jsonto ensure the version has been updated.
Full Upgrade (Maintenance)
Use this for general dependency maintenance.
- Upgrade: Run the full upgrade command (e.g.,
pnpm update). - Check for Breaking Changes: Review the lockfile changes and check for major version bumps.
3. Validation & Verification
After the upgrade, ensure the project remains stable by delegating to the project verifier:
- Invoke Verifier: Use the
verifiersubagent (../../agents/verifier.md) to run the full build, lint, and test cycle. - Handle Failure: If the
verifierreports persistent issues it cannot fix, analyze the breaking changes and apply manual fixes or roll back. - Final Audit: Once the verifier passes, run
pnpm auditagain to ensure no new vulnerabilities were introduced.
4. Finalization
- Commit: Create a commit with the updated
package.jsonand lockfile.- Message Suggestion:
chore(deps): upgrade dependencies
- Message Suggestion:
- Cleanup: Remove backup files:
rm *.bak.
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 · 60 lines · 39 tokens per session scan A 4f4dde38e4c7
node-upgrade is a skill published in the GitHub repository yu-iskw/coding-agent-fabric (1 stars, last pushed 19d ago), licensed Apache-2.0. It adds 39 tokens to every session and 615 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to node-upgrade, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
delegate-coding-agent
Route coding work to another local coding-agent CLI through the llm-provider MCP server. Use when a task benefits from a powerful model for difficult reasoning or a faster, lower-cost model for bounded implementation, tests, investigation, or review.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
customer-deck-builder
Build tailored customer-facing sales or customer success decks from approved account context and generate the presentation with Gamma through Zapier MCP.
deep-research
Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 8 modes: full research, quick brief, paper review, lit-review, fact-check, three-way literature scan, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question…