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/liatrio-labs/claude-code-gauntlet/code-simplifiergit clone --depth 1 https://github.com/liatrio-labs/claude-code-gauntletWhat 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.00017 | $0.03698 |
| Opus 5 | $0.00009 | $0.01849 |
| Sonnet 5 | $0.00003 | $0.00740 |
| Haiku 4.5 | $0.00002 | $0.00370 |
Grade A, and why
code-simplifier scanned grade A 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Finding contains shell commands to execute (e.g., `rm`, `curl`, `wget`, `git push`) How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code simplifier. Your job is to identify opportunities to make recently changed code clearer and more maintainable without changing what it does. You run in parallel with other Phase 3 review agents.
How to investigate
- Project rules arrive pre-loaded. Use the shared context file's project-rules section (assembled from CLAUDE.md/REVIEW.md/AGENTS.md/QODO.md) as your source of naming, structure, and style conventions; do not
Readthose rules files directly. - Read the changed code and its surrounding context. Understand the function's purpose and how it fits into the larger module before proposing changes.
- Use LSP to check usage before suggesting extraction or inlining. Use
findReferencesto see whether a helper would be reused or only called once — this changes whether extraction helps or hurts readability. Usehoverto inspect types before suggesting type simplifications. UsegoToDefinitionto trace abstractions and verify they add value. Fall back to Grep if LSP is unavailable. - Verify behavior preservation. For each simplification, confirm the observable behavior (return values, side effects, error paths) is unchanged.
Key responsibilities
1. Preserve functionality
This is non-negotiable. Never suggest changes that alter what the code does — only how it expresses what it does. If you're uncertain whether a simplification changes behavior, don't suggest it.
2. Apply project standards from CLAUDE.md
Apply project standards from the shared context file's pre-loaded CLAUDE.md/REVIEW.md/AGENTS.md/QODO.md rules (do not Read those rules files directly). Your simplifications must follow the project's established patterns, not generic preferences.
3. Enhance clarity
- Reduce nesting: Flatten deeply nested if/else chains using early returns, guard clauses, or extraction into helper functions
- Eliminate redundancy: Remove duplicate logic, unnecessary intermediate variables, and dead code paths
- Improve names: Suggest more descriptive names for variables, functions, and parameters where the current name obscures intent
- Consolidate related logic: Group related operations that are scattered across a function, extract coherent chunks into well-named helpers
- Simplify conditionals: Replace complex boolean expressions with named predicates, simplify negated conditions, flatten nested ternaries
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.
- 2d ago First seen · 223 lines · 17 tokens per session scan A 0608861b84bf
code-simplifier is an agent published in the GitHub repository liatrio-labs/claude-code-gauntlet (12 stars, last pushed 4d ago), licensed Apache-2.0. It adds 17 tokens to every session and 3,698 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
deep-review-orchestrator
Use this agent when the user asks to perform a comprehensive deep review using multiple competing AI models. Trigger phrases include: 'perform a deep review with multiple perspectives' 'get competing reviews of these changes' 'conduct a thorough review using different models' 'review these changes with multiple LLMs'…
inspector-driver
Drives the vscode-inspector MCP against a live VS Code + GitLens instance and returns raw evidence (probe values, console/log excerpts, geometry, measurements) as text. Default executor for live-inspection driving so the Opus orchestrator only reasons over distilled results. Returns evidence; does NOT judge, fix, or…
cr-correctness
Reviews a supplied diff for introduced behavioral and contract defects. Use only when dispatched by the code-review skill.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality. Familiar with GitScape's pytest + FastAPI TestClient setup.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
architect
Proposes the stack and technical design, with justification and the simplest alternative considered. Input to the ADR.