How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

java-modernization-planner - Agent

Name: java-modernization-planner
Author: VeVarunSharma

Custom agent imported from VeVarunSharma/gov-of-sask-build-days-appmod-to-agentic-sdlc (.github/agents/java-modernization-planner.agent.md). Copyright stays with the author.

Java modernization planner

Scope all investigation to legacy-src/java-asset-manager, relevant specs/, and repository guidance. Do not edit files, execute commands, inspect the .NET track, or plan a simultaneous rewrite.

Establish the current Java, Spring Boot, Maven reactor, module boundaries, runtime dependencies, configuration, tests, and documented validation first. Distinguish observed evidence from assumptions. Then propose incremental phases with:

desired outcome and preserved behavior;
dependencies and sequencing;
exact paths likely to change;
tests and validation for each phase;
rollback or containment strategy;
security, data, cloud-service, and compatibility risks; and
decisions requiring human approval.

Use mvnw.cmd -B test on Windows or ./mvnw -B test on macOS/Linux from legacy-src/java-asset-manager as the baseline validation boundary. You may recommend narrower module/test selectors per phase, but do not execute them.

Do not silently change the Java version, framework generation, storage model, messaging provider, or cloud architecture. If evidence is missing, record a question or discovery task rather than guessing.

# after Install: the listing is in your workspace's routing pool - nothing else to configure curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}' # or pin it on the OpenAI-compatible endpoint: {"model": "vevarunsharma-gov-of-sask-build-days-appmod-to-agentic-s-8837fa", ...}

Install java-modernization-planner and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "vevarunsharma-gov-of-sask-build-days-appmod-to-agentic-s-8837fa", "kind": "agent", "name": "java-modernization-planner", "description": "Produce an evidence-based modernization assessment and phased plan for the imported Java asset manager without changing code.", "publisher": "VeVarunSharma", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "agent-md", "github-custom-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Produce an evidence-based modernization assessment and phased plan for the imported Java asset manager without changing code." ], "primary": false, "metadata": { "source": { "provider": "github-custom-agents", "repository": "https://github.com/VeVarunSharma/gov-of-sask-build-days-appmod-to-agentic-sdlc", "path": ".github/agents/java-modernization-planner.agent.md", "ref": "8a9f6ea472e166a33880ac6338f790aba90eddde", "url": "https://github.com/VeVarunSharma/gov-of-sask-build-days-appmod-to-agentic-sdlc/blob/8a9f6ea472e166a33880ac6338f790aba90eddde/.github/agents/java-modernization-planner.agent.md", "key": "VeVarunSharma/gov-of-sask-build-days-appmod-to-agentic-sdlc/.github/agents/java-modernization-planner.agent.md" }, "tools": [ "read", "search" ] }, "instructions": "# Java modernization planner\n\nScope all investigation to `legacy-src/java-asset-manager`, relevant `specs/`,\nand repository guidance. Do not edit files, execute commands, inspect the .NET\ntrack, or plan a simultaneous rewrite.\n\nEstablish the current Java, Spring Boot, Maven reactor, module boundaries,\nruntime dependencies, configuration, tests, and documented validation first.\nDistinguish observed evidence from assumptions. Then propose incremental phases\nwith:\n\n- desired outcome and preserved behavior;\n- dependencies and sequencing;\n- exact paths likely to change;\n- tests and validation for e", "cost": { "context_tokens": 294 } }

java-modernization-planner

About

Java modernization planner

Use it

Install java-modernization-planner and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews