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.
npx agentmods add commands/teddy563/mcwrench/upgradegit clone --depth 1 https://github.com/Teddy563/mcwrenchWrote 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/teddy563/mcwrench/upgrade)<a href="https://agentmods.dev/commands/teddy563/mcwrench/upgrade"><img src="https://agentmods.dev/badge/commands/teddy563/mcwrench/upgrade.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.00250 |
| Opus 5 | $0.00012 | $0.00125 |
| Sonnet 5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
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 3d 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.
What it actually says
Use the server-doctor skill to plan an upgrade to $ARGUMENTS from the server-profile, following
references/upgrade-checklist.md.
Check: Java 25 requirement for Paper 26.1+ (flag UnsupportedClassVersionError risk); the 26.1
unobfuscated-jar break — label each installed plugin has-a-build / none / unknown via
node "${CLAUDE_PLUGIN_ROOT}/skills/server-doctor/scripts/check-plugin-versions.mjs" <root> +
learn-plugin-docs; do not combine a version bump with a software/server-type switch; back up and
trim before a world upgrade.
Emit the ordered runbook: back up → bump Java → update plugins (verify builds) → test on a copy → upgrade the world → re-audit. Read-only; confirm before any irreversible step and tell the user to back up first.
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.
- 3d ago First seen · 19 lines · 24 tokens per session scan A 5321a7c97fd4
upgrade is a command published in the GitHub repository Teddy563/mcwrench (1 stars, last pushed 10d ago), licensed MIT. It adds 24 tokens to every session and 250 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
migrate-catalog
Guided catalog migration flow. Extract Databricks Unity Catalog / HMS metadata, preview the 18-rule DDL rewrite, then batched replay on AIDP. Asks before destructive replay step.
speckit.taskstoissues
Command "speckit.taskstoissues" from akiojin/unity-mcp-server, covering ユーザー入力 and 実行手順.
models
List models available to the local Antigravity (agy) CLI.
pipeline-spec
Generate a CI/CD pipeline specification for a game project.
sync-check
Synchronize and report on parallel workstreams (Phase 5).
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.