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 roedyrustam/vibes-plug --skill dependency-upgrade-migratorgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/dependency-upgrade-migrator)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/dependency-upgrade-migrator"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/dependency-upgrade-migrator/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/roedyrustam/vibes-plug/dependency-upgrade-migrator"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/dependency-upgrade-migrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 9 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 64 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 65 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 66 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 69 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 70 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 71 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 205 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 238 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 239 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00052 | $0.03685 |
| Opus 5.5 | $0.00021 | $0.01474 |
| Sonnet 5.5 | $0.00010 | $0.00737 |
| Haiku 4.5 | $0.00005 | $0.00368 |
Grade A, and why
dependency-upgrade-migrator scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
// ✅ After: fetch(url, { cache: 'force-cache' }) for explicit caching How it starts
The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Upgrade Migrator (2026 Edition)
English
Orchestration & Integration
- Upstream & Lifecycle:
zero-to-prod-orchestrator(Phase 2 & Phase 7 upgrades),brainstorming,session-memory-manager. - Monorepos & Package Architecture:
monorepo-architect(pnpm catalogs & workspace dependency alignment),living-codebase-ast-graph(breaking change blast radius). - Quality Gates & Testing:
e2e-testing-expert(post-upgrade regression suites),autonomous-tdd-debugger(lockfile & test runner self-healing),production-ready-hardener(vulnerability audit). - CI/CD & Debt Cleanup:
ci-cd-devops-architect(Renovate bot pipelines),zero-tech-debt-auditor(dead code & deprecated API removal).
Description
Production-grade guide for safely upgrading dependencies, migrating through breaking changes, and maintaining healthy dependency trees. Covers automated upgrade tooling (npm-check-updates, taze, Renovate Bot), major framework migration guides (React 18→19, Next.js 14→15, Tailwind v3→v4), codemod automation (jscodeshift, ts-morph), vulnerability remediation (npm audit, pnpm audit), lockfile hygiene, monorepo alignment (pnpm catalogs), and breaking change detection workflows.
Trigger Conditions
Activate this skill when:
- Upgrading major versions of frameworks (React, Next.js, Tailwind, etc.).
- Running security audits and remediating vulnerabilities.
- Setting up automated dependency update bots (Renovate, Dependabot).
- Writing or running codemods for API migration.
- Cleaning up dependency trees and removing unused packages.
- Aligning dependency versions across monorepo packages.
1. Upgrade Strategy Matrix
| Upgrade Type | Risk Level | Strategy | Tools |
|---|---|---|---|
| Patch (1.0.x) | 🟢 Low | Auto-merge after tests pass | Renovate, Dependabot |
| Minor (1.x.0) | 🟡 Medium | Auto-merge with manual review | Renovate + test suite |
| Major (x.0.0) | 🔴 High | Manual review, migration guide, branch | Manual + codemods |
| Security (any) | 🔴 Critical | Immediate upgrade, hotfix | npm audit fix, manual |
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.
- 3d ago Changed · -4 lines d62a44b7c449
- 4d ago Changed · +1 lines d2fc94d2b17a
- 7d ago Changed · +78 lines 1d80742ee2d7
- 16d ago Changed 45593fc56cfd
- 21d ago Changed 7de4262cfdbc
- 22d ago Changed c79a037f1a44
- 24d ago Changed 540bf24d150b
- 25d ago Changed · -6 lines · +38 tokens per session 1acd14088ba1
- 26d ago Changed · +6 lines · -38 tokens per session 015f17ecea5d
- 1mo ago First seen · 302 lines · 52 tokens per session scan A 7a826edb0dc3
dependency-upgrade-migrator is a skill published in the GitHub repository roedyrustam/vibes-plug (113 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 3,685 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
code-review
Reviews code for bugs, security issues, and best practices.
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.
diagnosing-bugs
A structured process for diagnosing difficult software bugs and performance slowdowns. It starts by creating a repeatable pass-or-fail check, such as a failing test, HTTP request, command, or browser script.
mantis-patch
Generates minimal security fixes using transactional isolation (shadow directories or file backups), applies patches, and verifies them. Use when security findings are successfully reproduced and need patches applied and verified. Don't use for initial vulnerability research or reproduction payload generation.