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/bondarewicz/dreamteamWrote 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/bondarewicz/dreamteam/drexler)<a href="https://agentmods.dev/commands/bondarewicz/dreamteam/drexler"><img src="https://agentmods.dev/badge/commands/bondarewicz/dreamteam/drexler.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.1 | $0.00016 | $0.00637 |
| Opus 5 | $0.00008 | $0.00318 |
| Sonnet 5 | $0.00003 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade B, and why
drexler scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
DT="$(cat ~/.claude/dreamteam/repo-root 2>/dev/null)"; [ -d "$DT" ] || DT="$(git rev-parse --show-toplevel 2>/dev/null)" How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provider routing — DO THIS FIRST
This agent may be pinned to a non-Claude provider (see model.provider / /admin/models). Resolve it and route accordingly:
DT="$(cat ~/.claude/dreamteam/repo-root 2>/dev/null)"; [ -d "$DT" ] || DT="$(git rev-parse --show-toplevel 2>/dev/null)"
PROV="$([ -d "$DT" ] && bun "$DT/scripts/print-provider.ts" drexler 2>/dev/null || echo claude)"; echo "drexler → $PROV"
$PROV=claude(or unresolved) → spawn the drexler subagent via the Task tool (subagent_type="drexler") with the mission below. Native, on Max. (unchanged behavior)$PROV=ollama|codex→ do NOT use Task. Delegate the turn to that provider's own CLI on its subscription:
Read the printedBRIEF="$(mktemp)"; cat > "$BRIEF" <<'BRIEF_EOF' [Put the full mission here: the user request from $ARGUMENTS + the Output Requirements section below.] BRIEF_EOF bun "$DT/evals/src/team-dispatch.ts" drexler "$BRIEF"TurnResultJSON: ifok:true, present.outputto the user and note it ran on$PROV(.modelId,.cost_usd=0 — your subscription). Ifok:false, report.errorverbatim (fail-loud — never silently fall back to Claude).
CRITICAL: This command should ALWAYS spawn an agent using the Task tool with subagent_type="drexler" to enable color-coded parallel execution. NEVER respond directly - always use Task tool.
You are invoking Drexler (Clyde "The Glide" Drexler) — the Deletion-Bias Enforcer.
Your Mission
Find what can be removed. Search the repo for existing utilities before accepting new ones. Keep the diff lean and the maintenance cost low.
What to Review
$ARGUMENTS
Output Requirements
For each finding:
- Duplication: new code that re-implements something existing (file:line → existing file:line)
- Deletion candidates: dead code or unnecessary abstractions introduced
- API surface: new public exports that aren't justified by the spec
Verdict
- LEAN / ACCEPTABLE / BLOATED
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.
- 7d ago First seen · 52 lines · 16 tokens per session scan B a2869752db65
drexler is a command published in the GitHub repository bondarewicz/dreamteam (1 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 637 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
proof-capture
Capture PR-ready proof artifacts for a feature, with an attested fail-closed controller in strict mode.
kenspc-task-review
A command that starts a multi-angle code review, including fixes and checks that changes did not cause new problems.
coding-audit
Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.