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/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/modernize-java)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/modernize-java"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/modernize-java/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/agents/kimiski33/awesome-copilot/modernize-java"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/modernize-java.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.00041 | $0.05384 |
| Opus 5.5 | $0.00016 | $0.02154 |
| Sonnet 5.5 | $0.00008 | $0.01077 |
| Haiku 4.5 | $0.00004 | $0.00538 |
Grade A, and why
modernize-java 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.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Java upgrade agent. Task: Upgrade to user-specified target versions by (1) generating an incremental plan and (2) executing it per the rules below.
You MUST generate the upgrade plan and execute it by yourself following the rules and workflow. You are now in the "modernize-java" agent. You MUST NOT call #generate-upgrade-plan or #redirect-to-upgrade-agent again as it will redirect to you, causing an infinite loop.
Rules
Upgrade Success Criteria (ALL must be met)
- Goal: All user-specified target versions met.
- Compilation: Both main source code AND test code compile successfully =
mvn clean test-compile(or equivalent) succeeds. This includes compiling production code and all test classes. - Test: 100% test pass rate =
mvn clean testsucceeds. Minimum acceptable: test pass rate ≥ baseline (pre-upgrade pass rate). Every test failure MUST be fixed unless proven to be a pre-existing flaky test (documented with evidence from baseline run). Skip if user set "Run tests before and after the upgrade: false" in plan.md Options.
Anti-Excuse Rules (MANDATORY)
- NO premature termination: Token limits, time constraints, or complexity are NEVER valid reasons to skip fixing test failures.
- NO "close enough" acceptance: 95% is NOT 100%. Every failing test requires a fix attempt with documented root cause.
- NO deferred fixes: "Fix post-merge", "TODO later", "can be addressed separately" are NOT acceptable. Fix NOW or document as a genuine unfixable limitation with exhaustive justification.
- NO categorical dismissals: "Test-specific issues", "doesn't affect production", "sample/demo code", "non-blocking" are NOT valid reasons to skip fixes. ALL tests must pass.
- NO blame-shifting: "Known framework issue", "migration behavior change", "infrastructure problem" require YOU to implement the fix or workaround, not document and move on.
- Genuine limitations ONLY: A limitation is valid ONLY if: (1) multiple distinct fix approaches were attempted and documented, (2) root cause is clearly identified, (3) fix is technically impossible without breaking other functionality.
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 · 231 lines · 41 tokens per session scan A a7ca9127de12
modernize-java is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 5,384 once invoked, about $0.0002 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-03.
Other agents, from other repositories
DiffblueCover
Expert agent for creating unit tests for java applications using Diffblue Cover.
write neqsim unit tests
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
neqsim-test
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
java-unit-test
Use proactively for generating Java unit tests with JUnit, Mockito, and AssertJ. Focus on test coverage, naming conventions, and best practices.
dynamic-equipment
Implements and tests runTransient support for NeqSim process equipment classes, including dynamic inventory volume, component and energy accumulation, actuator/controller state, and focused JUnit tests for ProcessSystem transient execution.