What is Dependency Upgrade Plan?

A planning command for updating project dependencies, which are external libraries and packages a project uses. It groups updates by size and risk, checks for security problems, and identifies migrations needed for major-version changes.

Use it to inspect current dependency versions, prioritise security and unsupported packages, compare stable releases, and prepare a phased upgrade plan.

It turns a large list of available updates into staged work, while separating safer near-term updates from changes that may break existing code.

How arvindand/maven-tools-mcp configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to arvindand/maven-tools-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/arvindand/maven-tools-mcp/main/.github/prompts/upgrade-plan.prompt.md

Clone the repo

git clone --depth 1 https://github.com/arvindand/maven-tools-mcp

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/arvindand/maven-tools-mcp/upgrade-plan/github.svg)](https://agentmods.dev/commands/arvindand/maven-tools-mcp/upgrade-plan)

Your own site

<a href="https://agentmods.dev/commands/arvindand/maven-tools-mcp/upgrade-plan"><img src="https://agentmods.dev/badge/commands/arvindand/maven-tools-mcp/upgrade-plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/arvindand/maven-tools-mcp/upgrade-plan"><img src="https://agentmods.dev/badge/commands/arvindand/maven-tools-mcp/upgrade-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 517 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00013	$0.00517
Opus 5.5	$0.00005	$0.00207
Sonnet 5.5	$0.00003	$0.00103
Haiku 4.5	$0.00001	$0.00052

Measured 1mo ago against content hash a78980558ddb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Dependency Upgrade Plan 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.

.github/prompts/upgrade-plan.prompt.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dependency Upgrade Plan

Generate a phased upgrade plan for project dependencies using maven-tools-mcp.

Instructions

Analyze Current State
- Extract all dependencies with current versions from build file
- Use compare_dependency_versions with includeSecurityScan=true and stabilityFilter=STABLE_ONLY to find available updates
- Use analyze_project_health for health assessment
Categorize Updates
- Patch updates: Bug fixes, safe to apply
- Minor updates: New features, generally backward compatible
- Same-major fallback updates: Safer near-term targets when the latest stable release is a major jump
- Major updates: Breaking changes, require migration
Prioritize by Risk
- Security vulnerabilities (highest priority)
- End-of-life or unmaintained dependencies
- Stale dependencies (>1 year old)
- General updates
Check for Breaking Changes
- For major updates, note migration requirements
- If same_major_stable_fallback exists, keep that as the near-term recommendation and the major target as a separate migration track
- Use Context7 guidance hints for migration documentation

Upgrade Plan Format

Phase 1: Critical Security Fixes

Dependencies with known vulnerabilities that need immediate attention.

Dependency	Current	Target	Type	Risk

Phase 2: Immediate Safe Updates

Patch updates and same-major fallback updates that can be taken before any major migration.

Dependency	Current	Target

Phase 3: Planned Minor Updates

Minor updates that are still worth testing thoroughly before deploying.

Dependency	Current	Target	Notable Changes

Phase 4: Major Updates

Breaking changes, plan migration carefully.

Dependency	Current	Target	Migration Notes

Read the full file on GitHub · 84 lines

Changes

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 · 84 lines · 13 tokens per session scan A a78980558ddb

Subscribe to this mod's changes

Dependency Upgrade Plan is a command published in the GitHub repository arvindand/maven-tools-mcp (35 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 517 once invoked, about $0.0001 per session on Opus 5.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-09-07.

Planning Security ai-tools dependency-management developer-tools docker graalvm gradle

domains

Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.

gotempsh/temps · 0 tokens

synthesise-reviews

Deduplicate and reconcile multiple completed review reports into one prioritised revision plan with conflicts and dependencies made explicit. Use when parallel reviewers have returned findings that need a single action sequence. Not for running the reviews; use $review-cluster.

flonat/flonat-research · 47 tokens

audit-code

When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.

KaelSensei/MagicAIBuilder · 0 tokens

firebase-publish

Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.

Pierry/harness-kit · 20 tokens

auditoria-legal

Grupo: Trabajo con el framework En una frase: Auditoría de cumplimiento legal del producto — territorio, evidencia y lo que el código no cubre. Cuándo: Antes de publicar una app o web: registro, cookies, analítica, emails, suscripciones, contenido de usuarios. Quién: Cualquier operador del repo.

Mazalucas/El-DT-Lightweight-Army · 0 tokens

scan

Scan AWS account for cost optimization.

prajapatimehul/claude-aws-cost-saver · 6 tokens

maven-tools-mcp: Command for GitHub Copilot