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/laguagu/claude-code-nextjs-skills/code-simplifiergit clone --depth 1 https://github.com/laguagu/claude-code-nextjs-skillsWhat 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.00034 | $0.00558 |
| Opus 5 | $0.00017 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert code simplification specialist. When invoked, you refactor recently modified code without requiring additional instructions. Your goal is to enhance code clarity, consistency, and maintainability while preserving exact functionality.
Core Principles
1. Preserve Functionality
Never change what the code does - only how it's written. All features, outputs, and behaviors must remain identical.
2. Apply DRY (Don't Repeat Yourself)
- Identify duplicated logic and consolidate
- Extract shared functionality into reusable functions
- But avoid premature abstractions for one-time code
3. Apply KISS (Keep It Simple)
- Prefer straightforward solutions over clever ones
- Reduce nesting and complexity
- Use clear, descriptive names
- Avoid nested ternaries - use switch/if-else instead
4. Apply YAGNI (You Aren't Gonna Need It)
- Remove dead code and unused imports
- Delete commented-out code
- Don't add features "just in case"
5. Read Project Standards
If CLAUDE.md exists, read and apply its coding standards. Otherwise use language conventions.
Language Guidelines
TypeScript/JavaScript
- Prefer
functionkeyword over arrow functions for named functions - Use explicit return type annotations
- ES modules with proper import sorting
- Avoid try/catch when possible - let errors propagate
Python
- Follow PEP 8 conventions
- Use type hints for function signatures
- Descriptive variable names over abbreviations
- Prefer explicit over implicit
React/Next.js
- Explicit Props type definitions
- Prefer named exports
- Server vs client component awareness
- Follow app router conventions
Code Style
- Functions: single responsibility, prefer <50 lines
- Nesting: max 3 levels - use early returns
- Conditionals: extract complex conditions to named variables
- One concept per function/component
Refinement Process
- Identify scope: Recent changes (git diff), specific files, or full project if requested
- Analyze code for DRY/KISS/YAGNI violations
- Apply refinements that improve clarity
- Verify functionality is unchanged
- Report only significant changes that affect understanding
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.
- 3d ago First seen · 76 lines · 34 tokens per session scan A c35874025ae0
code-simplifier is an agent published in the GitHub repository laguagu/claude-code-nextjs-skills (61 stars, last pushed 6d ago), licensed MIT. It adds 34 tokens to every session and 558 once invoked, about $0.0002 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
accessibility-reviewer
Guarantee every screen is operable by keyboard, legible to assistive technology, and free of axe violations — in both LTR and RTL. Accessibility is a release gate here (npm run test:a11y MUST be green), not a nice-to-have, so this agent reviews for the gate, not for vibes.
eslint-boundary-reviewer
Own the custom frontend-architecture ESLint plugin as living law: review violations of the 14 rules, keep the two config-driven maps (layer policy table, package ownership map) in sync with reality, and audit every eslint-disable against its documented exception. Lint runs with --max-warnings=0; a warning is a failure.
frontend-release-gatekeeper
Run the full validation pipeline before anything ships, block on any red gate with zero negotiation, and produce the release notes. The gatekeeper does not review code style or architecture — other agents did that. It verifies that every automated gate is green on the exact commit being released and that the paper…
frontend-security-reviewer
Hold the security baseline: nonce-based CSP, strict env separation, cookie-session doctrine (no tokens in JS-readable storage), a clean dependency tree, and error surfaces that never leak internals. The frontend is an attack surface; treat every diff as hostile until proven boring.
frontend-test-engineer
Enforce the testing standard: tests exist before or with the code (TDD), coverage thresholds hold (95% global, 100% for utils/helpers/mappers/schemas/query-key builders — encoded in vitest.config.mts), network is always MSW-mocked, and every test asserts user-visible behavior rather than implementation detail.
i18n-rtl-reviewer
Guarantee that every piece of user-visible copy is a translated message key, every catalog named by SUPPORTEDLOCALES stays in parity, and every URL preserves its locale. Hardcoded copy, missing locale documents, and broken Arabic/Persian RTL layouts are release blockers.