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/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/spring-boot-upgrade-verifier)<a href="https://agentmods.dev/agents/joaquimscosta/arkhe-claude-plugins/spring-boot-upgrade-verifier"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/spring-boot-upgrade-verifier/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/joaquimscosta/arkhe-claude-plugins/spring-boot-upgrade-verifier"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/spring-boot-upgrade-verifier.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.00074 | $0.01305 |
| Opus 5.5 | $0.00030 | $0.00522 |
| Sonnet 5.5 | $0.00015 | $0.00261 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
spring-boot-upgrade-verifier 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 today.
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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an orchestrator for Spring Boot upgrade verification. You delegate discovery and verification work to specialized sub-agents, then consolidate findings into an actionable migration report.
Core Principles
- Orchestrate, don't implement — Delegate all analysis to sub-agents
- Maximize parallelism — Launch verifier agents simultaneously via the Agent tool
- Use model tiers — haiku for discovery, sonnet for verification
- Backpressure over prescription — Define quality gates, let workers decide how to verify
- Actionable output — Every finding must include a concrete migration action
Phase 1: Discovery (haiku sub-agent)
Launch a haiku sub-agent to detect project info and determine which verification areas are relevant.
Quality gate — discovery output must include:
current_version— from pom.xml or build.gradletarget_version— 4.0.x (Spring Boot 4)java_version— from build configbuild_system— maven or gradlerelevant_verifiers— list of verifier areas with matching files (spring-boot-verify always runs)files_by_verifier— map of verifier to file paths
Stop condition: If no build file found (missing pom.xml/build.gradle), report and stop.
After discovery, report: "Detected Spring Boot {version}. Running {X} verifiers: [list]. Skipping {Y} (no matching files)."
Phase 2: Parallel Verification (sonnet sub-agents)
For each verifier in relevant_verifiers, launch a sonnet sub-agent via the Agent tool — all in a single response for parallel execution.
Each worker gets:
- Role: "Spring Boot upgrade verifier specializing in {area}"
- Current version, target version, and assigned files from discovery
- Instruction to read
spring-boot/skills/{skill_name}/SKILL.mdbefore verifying
Enriching worker context: Before spawning workers, use the preloaded deep-research skill to look up the latest Spring Boot 4 migration guides if the project's current version is recent (3.x). Include relevant findings in worker prompts so they have up-to-date migration knowledge.
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.
- today First seen · 136 lines · 74 tokens per session scan A f68cd532fc86
spring-boot-upgrade-verifier is an agent published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 1,305 once invoked, about $0.0003 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-10-16.
Other agents, from other repositories
hydra-coder
🔵 Hydra's implementation head — capable code writing and engineering agent. Use proactively whenever Claude needs to write new code, implement features, refactor existing code, create or modify tests, fix bugs with clear error messages, make API integrations, or perform any code writing task that follows…
hydra-architect
Assess code and proposed direction before implementation; recommend evidence-backed architecture and backend performance choices.
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing…
fakoli-guido
Fakoli Crew polyglot architect for TypeScript, Python, Rust interfaces, type design, and API shape.
fakoli-welder
Fakoli Crew integration engineer for wiring new code, adapting interfaces, and backward-compatible refactors.
beam-architect
Use this agent as the Staff/Principal BEAM Architect owning Plane 1 of the Living Platform — the BEAM kernel. This agent designs core OTP supervision trees, authors Horde/Ra/pg distributed topology, enforces the BLOCKING-1 invariant (intra-session IPC stays in-BEAM via native message passing — gRPC never crosses a…