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/diagnosegit 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/diagnose)<a href="https://agentmods.dev/commands/teddy563/mcwrench/diagnose"><img src="https://agentmods.dev/badge/commands/teddy563/mcwrench/diagnose.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.00016 | $0.00242 |
| Opus 5 | $0.00008 | $0.00121 |
| Sonnet 5 | $0.00003 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
diagnose 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 4d 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 diagnose $ARGUMENTS (a crash-reports/crash-*.txt or
logs/latest.log file, a server root, or pasted log text).
Run:
node "${CLAUDE_PLUGIN_ROOT}/skills/server-doctor/scripts/parse-log.mjs" $ARGUMENTS
(or pipe the pasted log to it; add --json for machine output).
Report the ranked root cause: name the likely culprit plugin namespace and a fix per finding,
prioritised critical to low (Java/class-version, OOM, Watchdog/overload, ticking entity/world, port
bind, EULA, plugin load/dependency, NoClassDefFound). Route a named plugin to learn-plugin-docs
and lag findings to performance-tuning; cross-check the server-profile. Read-only; never run live
commands and never invent a fix.
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.
- 4d ago First seen · 19 lines · 16 tokens per session scan A 3ea1fc7989dc
diagnose is a command published in the GitHub repository Teddy563/mcwrench (1 stars, last pushed 11d ago), licensed MIT. It adds 16 tokens to every session and 242 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.
mindforge:gaming
Design gaming backend architecture. Usage: /mindforge:gaming [feature] [--mode realtime|turn-based] [--scale small|massive].
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.