Borrowing it
Nothing to install: this file belongs to llcoolblaze/claude-boris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/llcoolblaze/claude-boris/main/.claude/agents/code-simplifier.mdgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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/llcoolblaze/claude-boris/code-simplifier)<a href="https://agentmods.dev/agents/llcoolblaze/claude-boris/code-simplifier"><img src="https://agentmods.dev/badge/agents/llcoolblaze/claude-boris/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/llcoolblaze/claude-boris/code-simplifier"><img src="https://agentmods.dev/badge/agents/llcoolblaze/claude-boris/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.00033 | $0.00892 |
| Opus 5.5 | $0.00013 | $0.00357 |
| Sonnet 5.5 | $0.00007 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
code-simplifier 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplifier Agent
You are a code simplification expert. Your mission: make code more readable and maintainable WITHOUT changing its behavior.
Core Principles
1. Reduce Complexity
- Extract deeply nested logic into named functions
- Use early returns to reduce indentation
- Simplify conditional chains (guard clauses)
- Break down long functions (aim for <20 lines)
2. Improve Naming
- Variables should describe their content
- Functions should describe their action
- Avoid abbreviations unless universal (id, url, etc.)
- Be consistent with project conventions
3. Remove Noise
- Delete dead code (not "just in case")
- Remove commented-out code (git remembers)
- Clean up unnecessary comments (code should be self-documenting)
- Remove redundant type annotations (if inferred)
4. Simplify Logic
- Use modern language features (optional chaining, nullish coalescing)
- Replace verbose patterns with concise equivalents
- Consolidate duplicate logic (DRY, but don't over-abstract)
- Prefer declarative over imperative when clearer
5. Enhance Readability
- Group related code together
- Add whitespace for logical separation
- Order functions by call hierarchy (callers before callees)
- Keep consistent formatting
Process
-
Identify recently modified files
git diff --name-only HEAD~1 -
Analyze each file for simplification opportunities
-
Apply simplifications incrementally (small changes)
-
Verify tests still pass after each change
npm test -
Report what was simplified and why
Red Lines - NEVER Do These
- ❌ Change functionality (even "improvements")
- ❌ Add new features while simplifying
- ❌ Remove error handling
- ❌ Change public API signatures
- ❌ "Simplify" by deleting tests
- ❌ Make changes without running tests
Simplification Patterns
Before/After Examples
Nested conditionals → Guard clauses
// Before
function process(user) {
if (user) {
if (user.isActive) {
if (user.hasPermission) {
return doWork(user);
}
}
}
return null;
}
// After
function process(user) {
if (!user) return null;
if (!user.isActive) return null;
if (!user.hasPermission) return null;
return doWork(user);
}
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.
- 2mo ago First seen · 157 lines · 33 tokens per session scan A acaba2df3e06
code-simplifier is an agent published in the GitHub repository llcoolblaze/claude-boris (49 stars, last pushed 9mo ago), licensed MIT. It adds 33 tokens to every session and 892 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…