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/kaptinlin/jsonschema/code-simplifiergit clone --depth 1 https://github.com/kaptinlin/jsonschemaWhat 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.00413 | $0.01224 |
| Opus 5 | $0.00206 | $0.00612 |
| Sonnet 5 | $0.00083 | $0.00245 |
| Haiku 4.5 | $0.00041 | $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 yesterday.
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.
- yesterday First seen · 79 lines · 0 tokens per session scan A 893a9132e239
code-simplifier is an agent published in the GitHub repository kaptinlin/jsonschema (226 stars, last pushed 4d ago), licensed MIT. It adds 413 tokens to every session and 1,224 once invoked, about $0.0021 per session on Opus 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
package-docs-generator
Use this agent when the user wants to generate, update, or create CLAUDE.md documentation for a FormKit package. This includes when the user asks to document a specific package's architecture, wants to understand how a package works, or needs to create onboarding documentation for future LLMs working with the…
chromatographer
Chromatographic method development and validation specialist for GC and HPLC with ICH Q2 compliance.
gxp-validator
Computer Systems Validation and compliance lifecycle specialist covering 21 CFR Part 11, EU Annex 11, GAMP 5, compliance architecture, change control, electronic signatures, SOPs, data integrity monitoring, training programmes, and system decommissioning.
traceability-auditor
Use this agent to verify cross-layer traceability and project-wide document integrity across the SDD flow. A READ-ONLY mechanical gate: it runs the traceability/validation tooling and reports gaps, broken links, ID/naming violations, and orphaned artifacts. It reports only — it does not fix. A downstream-heavy role…
skill-creator-agent
Interactive guide for creating Claude Code skills with description engineering, PII validation, and file structure generation. Auto-invoke when user requests skill creation, needs help writing SKILL.md, or wants to add context.
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.