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/liatrio-labs/claude-code-gauntletWrote 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/liatrio-labs/claude-code-gauntlet/code-simplifier)<a href="https://agentmods.dev/agents/liatrio-labs/claude-code-gauntlet/code-simplifier"><img src="https://agentmods.dev/badge/agents/liatrio-labs/claude-code-gauntlet/code-simplifier/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/liatrio-labs/claude-code-gauntlet/code-simplifier"><img src="https://agentmods.dev/badge/agents/liatrio-labs/claude-code-gauntlet/code-simplifier.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.03733 |
| Opus 5.5 | $0.00007 | $0.01493 |
| Sonnet 5.5 | $0.00003 | $0.00747 |
| Haiku 4.5 | $0.00002 | $0.00373 |
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 1mo 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 — 224 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 review-rules and project-rules blocks (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.
- 1mo ago Changed 624a5c11a5a4
- 1mo ago Changed · +1 lines cdd0a7cc6f5c
- 1mo 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 (13 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 3,733 once invoked, about $0.0001 per session on Opus 5.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
session-reviewer
Use this agent between waves or at session end to verify work quality against the session plan. Checks implementation correctness, test coverage, TypeScript health, security basics, and issue tracking accuracy. Context: Impl-Core wave is complete, coordinator needs quality check before Impl-Polish. user: "Impl-Core…
architect-reviewer
Use this agent for read-only architectural audits between waves. Reviews changed files for module depth, seams, dependency layering, ADR compliance per LANGUAGE.md vocabulary. Context: After Impl-Core wave shipped 8 files. user: "Audit the W2 architecture before proceeding." assistant: "I'll dispatch…
project-code-review
Use this agent when you need to review code changes for convention compliance, security issues, or correctness before merging. Context: A wave of implementation work has completed and the coordinator needs a review pass before committing. user: "Review the auth module changes" assistant: "I'll use the…
design-reviewer
Reviews code for maintainability, readability, and structural design quality. Read-only.
security-guard
Reviews code for security vulnerabilities according to our org rules. Read-only.
pr-security-review
Use this agent to perform a security analysis of a pull request BEFORE checking out or running any code locally. Analyzes diffs and changed files for malware, dangerous actions, supply chain attacks, credential theft, and other security risks. Returns a verdict of SAFE, REVIEW NEEDED, or BLOCK. Must be run before any…