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 skills/yu-iskw/skill-inspector/node-upgradenpx skills add yu-iskw/skill-inspector --skill node-upgradegit clone --depth 1 https://github.com/yu-iskw/skill-inspectorWrote 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/skill-inspector/node-upgrade)<a href="https://agentmods.dev/skills/yu-iskw/skill-inspector/node-upgrade"><img src="https://agentmods.dev/badge/skills/yu-iskw/skill-inspector/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.00039 | $0.00615 |
| Opus 5 | $0.00019 | $0.00308 |
| Sonnet 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 5d 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:
- node-upgrade — 100% identical, 0 lines differ
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.
- 5d ago First seen · 60 lines · 39 tokens per session scan A 4f4dde38e4c7
node-upgrade is a skill published in the GitHub repository yu-iskw/skill-inspector (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 39 tokens to every session and 615 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
performing-sca-dependency-scanning-with-snyk
This skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and…
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
aod-orchestrate
Multi-feature orchestration skill that bridges /aod.blueprint output to parallel wave execution. Groups synced GitHub Issues by ICE priority tier (P0/P1/P2) into sequential waves, creates Task records, spawns batch sessions via the orchestrator API, monitors completion, and reports results. Supports --issues…