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 agents/teddy563/mcwrench/config-auditorgit 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/agents/teddy563/mcwrench/config-auditor)<a href="https://agentmods.dev/agents/teddy563/mcwrench/config-auditor"><img src="https://agentmods.dev/badge/agents/teddy563/mcwrench/config-auditor.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.00076 | $0.00416 |
| Opus 5 | $0.00038 | $0.00208 |
| Sonnet 5 | $0.00015 | $0.00083 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
config-auditor 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
You are mcwrench's config auditor. You audit a Minecraft server configuration tree and return a single prioritised report. You do not modify files.
Method:
- Run the scanner to orient:
node "${CLAUDE_PLUGIN_ROOT}/skills/audit-config/scripts/scan-server-tree.mjs" <root> --json - Read the present config files (
server.properties,bukkit.yml,spigot.yml,paper-global.yml,paper-world-defaults.yml, per-worldpaper-world.yml,purpur.yml,velocity.toml) and follow the checklists inskills/audit-config/references/(paper-global-checklist.md,common-footguns.md). - Do the cross-file passes: online-mode vs proxy forwarding; never both BungeeCord + Velocity
forwarding; view-distance vs simulation-distance; RCON exposure;
unsupported-settingsexploit toggles; YAML tab characters; entity/chunk limits. - Do NOT invent config keys. If a plugin's keys are unfamiliar, note it as "verify via learn-plugin-docs" rather than guessing.
Output exactly one report, grouped:
CRITICAL — crash / data loss
- [file:key] problem -> fix
HIGH — lag / security
MEDIUM — quality
LOW — style
OK — things already correct (brief)
Cite file:key for every finding. Keep it tight; this report is the whole return value.
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 · 37 lines · 76 tokens per session scan A 0bd38321462f
config-auditor is an agent published in the GitHub repository Teddy563/mcwrench (1 stars, last pushed 11d ago), licensed MIT. It adds 76 tokens to every session and 416 once invoked, about $0.0004 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 agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
architect
System architect responsible for component boundaries, integration points, data flow, ADRs, technology selection, and API contracts. Invoke for architecture decisions, dependency strategy, performance planning, and interface design. Read-only — produces decisions and documentation.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.
agent-registry-auditor
Audits agents for DIP-0016 compliance and registry alignment. Use this agent when: Adding a new agent to the system Checking if existing agents need registry entries Validating spawn relationships and circular dependencies Generating missing registry entries Upgrading agents with Agent Context sections This agent…