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.
git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitWrote 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/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.upgrade-dependencies)<a href="https://agentmods.dev/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.upgrade-dependencies"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.upgrade-dependencies/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/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.upgrade-dependencies"><img src="https://agentmods.dev/badge/commands/giuseppe-trisciuoglio/developer-kit/devkit.java.upgrade-dependencies.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.00035 | $0.02622 |
| Opus 5.5 | $0.00014 | $0.01049 |
| Sonnet 5.5 | $0.00007 | $0.00524 |
| Haiku 4.5 | $0.00003 | $0.00262 |
Grade A, and why
devkit.java.upgrade-dependencies 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://spring.io/projects/spring-boot | grep -A 5 "supported versions" How it starts
The opening of the file, as written. The whole thing — 462 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Java Dependency Upgrade Strategy
Overview
Plan and execute safe, incremental upgrades of Java project dependencies with minimal risk, proper testing, and clear migration paths for breaking changes.
Manages safe and incremental dependency upgrades for Java/Maven/Gradle projects with breaking change detection and migration guides. Use when upgrading project dependencies or migrating to new library versions.
Usage
/devkit.java.upgrade-dependencies $ARGUMENTS
Arguments
$1 specifies the scope (optional - defaults to all):
all- Analyze all dependenciesspring- Focus on Spring Boot and Spring Framework dependenciestesting- Focus on test dependencies (JUnit, Mockito, AssertJ, Testcontainers)security- Prioritize security vulnerabilitiesdirect- Only direct dependencies (not transitive)<groupId:artifactId>- Specific dependency (e.g.,org.springframework.boot:spring-boot-starter-web)
$2 specifies the strategy (optional - defaults to analyze):
analyze- Analyze and report available updates with risk assessmentplan- Create detailed upgrade plan with incremental stepsmigrate- Generate migration guide for major version upgradesexecute- Execute planned upgrades (requires confirmation)rollback- Create rollback strategy and backup current state
$3 specifies target version for specific dependency upgrades (optional):
- Version number (e.g.,
3.2.0,5.3.31) latest- Latest stable releaselatest-minor- Latest minor versionlatest-patch- Latest patch version
Execution Instructions
Agent Selection: To execute this task, use the following agent with fallback:
- Primary:
java-security-expert - If not available: Use
developer-kit:java-security-expertor fallback togeneral-purposeagent withspring-boot-crud-patternsskill
Context
- Build system: !
ls -la | grep -E "(pom\.xml|build\.gradle|build\.gradle\.kts)" - Current dependencies: !
if [ -f pom.xml ]; then mvn dependency:tree | head -30; elif [ -f build.gradle ]; then ./gradlew dependencies --configuration compileClasspath | head -30; fi - Outdated dependencies: !
if [ -f pom.xml ]; then mvn versions:display-dependency-updates 2>/dev/null | grep -E "\\->" | head -20; elif [ -f build.gradle ]; then ./gradlew dependencyUpdates 2>/dev/null | grep -E "\\->" | head -20; fi
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 · 462 lines · 35 tokens per session scan A 13541a1a5f51
devkit.java.upgrade-dependencies is a command published in the GitHub repository giuseppe-trisciuoglio/developer-kit (360 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 2,622 once invoked, about $0.0001 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-09-10.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.