17,588 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Multi-LLM Task Router Suite. runagent.py routes bounded tasks to six backends: Claude CLI, GitHub Copilot, Gemini CLI, Antigravity (Agy), Codex/OpenAI-compatible, and direct local Gemma 4 12B via llama-server (2s, no proxy). 11 expert agent personas covering adversarial patterns (red-team, debate synthesis, output va.
★not rated 6
changed yesterdayA
tokens not measured
originalMIT
A deterministic guardrail your coding agent runs on itself — structured findings on just the changed lines, before the code reaches disk. Zero LLM tokens, 0 false blocks.
★not rated 5 1mo agoA
tokens not measured
originalApache-2.0
The specialist lanes and memory that the built-in /code-review doesn't have. Invokes the built-in engine for general bug-finding (quick/standard/deep map to its effort levels), then adds what it lacks: a mechanical hallucinated-imports validator (lockfile-verified across Python/JS/TS/Rust/Go, with a vendored denylist…
★not rated 5 25d agoA
tokens not measured
originalApache-2.0
Turn Claude Code into a structured development partner — session lifecycle, named code reviewers, research pipelines, and 35+ workflow skills that enforce quality from plan through execution.
Code ownership session that turns AI-written code into understood code. The agent shortlists "vibe-y" pieces from recent changes, checks the user's confidence, then guides explain/reimplement/test exercises in a LeetCode-style format and captures distilled per-piece ownership notes — all without silently mutating the…
Use when verifying implementation work and the failure mode is superficial approval, code-reading in place of execution, or over-trusting a passing test suite without trying to break the change.
Splits a large change into small, single-purpose units of review — PRs, diffs, or CLs — each making one argument (one diff, one thesis) and each buildable and testable on its own. Use when a change is too big to review, when a feature builds on existing code, when working in a large monorepo with stacked diffs, or…
Full development workflow orchestrator: brainstorm → plan → worktree → convergent TDD/review loop → verify → PR. One human gate (spec approval); all other gates auto-proceed. Use when starting a feature or significant change from scratch. Usage: /mx-flow ; /mx-flow status [name]; /mx-flow finish .
Use in a dedicated subagent for post-TDD blind unit-test review against requirements and public contracts to find missing cases, wrong assertions, and brittle tests.
Review pull requests and code changes for actionable correctness, regression, security, compatibility, and test issues. Use for read-only PR review passes that must produce concise human findings plus a machine-readable verdict.
★not rated 5 2d agoA41 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: