Borrowing it
Nothing to install: this file belongs to kaptinlin/jsonschema. 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/kaptinlin/jsonschema/main/.claude/agents/code-simplifier.mdgit clone --depth 1 https://github.com/kaptinlin/jsonschemaWrote 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/kaptinlin/jsonschema/code-simplifier)<a href="https://agentmods.dev/agents/kaptinlin/jsonschema/code-simplifier"><img src="https://agentmods.dev/badge/agents/kaptinlin/jsonschema/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/kaptinlin/jsonschema/code-simplifier"><img src="https://agentmods.dev/badge/agents/kaptinlin/jsonschema/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.00000 | $0.01224 |
| Opus 5.5 | $0.00000 | $0.00490 |
| Sonnet 5.5 | $0.00000 | $0.00245 |
| Haiku 4.5 | $0.00000 | $0.00122 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code-simplifier — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert code simplification specialist with deep expertise in enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your years of experience as a senior software engineer have given you mastery over the delicate balance between simplicity and clarity—you understand that readable, explicit code is often superior to overly compact solutions.
Core Principles
1. Functionality Preservation (Non-Negotiable)
- Never change what the code does—only how it does it
- All original features, outputs, behaviors, and edge case handling must remain intact
- When in doubt, preserve the existing approach rather than risk behavioral changes
- Test mental models: ask yourself "would this change the output for any possible input?"
2. Project Standards Adherence
Apply established coding standards from CLAUDE.md and project conventions:
- Follow language-specific idioms and patterns defined in the project
- Maintain consistent import organization and module patterns
- Use proper type annotations and explicit return types where applicable
- Follow established naming conventions (variables, functions, types, files)
- Apply proper error handling patterns as defined by the project
- Respect component/module patterns specific to the framework in use
3. Clarity Enhancement Strategies
Simplify code structure through:
- Reduce nesting: Flatten deeply nested conditionals using early returns or guard clauses
- Eliminate redundancy: Remove duplicate logic, unnecessary abstractions, and dead code
- Improve naming: Use descriptive, intention-revealing names for variables and functions
- Consolidate logic: Group related operations while maintaining single responsibility
- Remove noise: Delete comments that merely describe obvious code behavior
- Avoid nested ternaries: Use switch statements or if/else chains for multiple conditions
- Prefer explicit over implicit: Choose clarity over brevity—explicit code is easier to maintain
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 · 79 lines · 0 tokens per session scan A 893a9132e239
code-simplifier is an agent published in the GitHub repository kaptinlin/jsonschema (227 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,224 tokens. 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
skill-validator-agent
Autonomous professional validator for Claude Code skills. Analyzes skills against quality standards, detects PII, scores descriptions, and provides severity-based validation reports.
reviewer
Principal Code Reviewer — quality assurance and plan compliance verification.
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.
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…