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/commands/joaquimscosta/arkhe-claude-plugins/verify-upgrade)<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/verify-upgrade"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/verify-upgrade/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/joaquimscosta/arkhe-claude-plugins/verify-upgrade"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/verify-upgrade.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.00012 | $0.00397 |
| Opus 5.5 | $0.00005 | $0.00159 |
| Sonnet 5.5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
verify-upgrade 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.
What it actually says
Spring Boot Upgrade Verification
Verify a Spring Boot project's readiness for upgrading to Spring Boot 4 using parallel multi-skill analysis.
Scope
$ARGUMENTS
Instructions
Use the Agent tool to invoke the spring-boot-upgrade-verifier agent with the scope above.
The agent orchestrates a 3-phase verification:
Phase 1: Discovery (haiku)
- Detect build system (Maven/Gradle) and current Spring Boot version
- Identify Java version
- Determine which verification areas have files to check
- Skip verifiers with no matching files
Phase 2: Parallel Verification (sonnet agents)
- Launch skill-specific verifier agents IN PARALLEL
- Each verifier reads skill docs and checks assigned files
- Categorize findings by severity (Critical/Error/Warning)
Phase 3: Migration Report
- Consolidate findings from all verifiers
- Generate unified migration checklist
- Provide actionable remediation steps
What Gets Verified
| Area | Checks |
|---|---|
| Dependencies | Jackson 3 migration, Undertow removal, javax→jakarta |
| Security | Lambda DSL, requestMatchers, authorizeHttpRequests |
| Testing | @MockitoBean, Testcontainers 2.x, slice tests |
| Observability | Actuator limits, trace sampling, OpenTelemetry |
Severity Levels
| Severity | Meaning |
|---|---|
| Critical | Blocks upgrade, must fix before proceeding |
| Error | Will break functionality after upgrade |
| Warning | Recommended for best practices |
Example Usage
# Verify entire project
/verify-upgrade
# Verify specific module
/verify-upgrade the order module
# Verify from specific path
/verify-upgrade src/main/java/com/example/
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 · 65 lines · 12 tokens per session scan A 4966f1ab5d77
verify-upgrade is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 397 once invoked, about $0.0000 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 commands, from other repositories
guard
Manually run the Hydra security and quality scan on specified files or directories.
cleanup
You are executing the /dogma:cleanup command. Your task is to find and fix AI-typical patterns in the codebase that reveal AI/agent usage.
lint
You are executing the /dogma:lint command. Your task is to detect the project type and run appropriate linting and formatting tools on staged files before commit.
perf
Structured performance investigation with baselines, profiling, and evidence-backed decisions.
p6-exploratory
Conducts unstructured, experience-based tests that automated tests and defined test cases do not cover. The goal is to find unexpected behaviours, usability issues, and hidden bugs that remain invisible in structured testing.
p8-ops
Analyses production errors and performance issues, evaluates incidents, and initiates countermeasures. Called reactively for specific incidents or proactively for regular operational reviews.