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 skills/valorvie/custom-skills/code-simplifiernpx skills add ValorVie/custom-skills --skill code-simplifiergit clone --depth 1 https://github.com/ValorVie/custom-skillsWrote 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/skills/valorvie/custom-skills/code-simplifier)<a href="https://agentmods.dev/skills/valorvie/custom-skills/code-simplifier"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/code-simplifier.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.00742 |
| Opus 5 | $0.00020 | $0.00371 |
| Sonnet 5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplifier
Overview
Simplify touched code without changing behavior. Prefer explicit, readable code over clever or overly compact rewrites, and keep scope limited to the files or sections the user just changed unless they request broader cleanup.
When to Use
- The user asks to "simplify", "clean up", "tidy", or "refactor without changing behavior"
- Recently modified code works, but has duplication, deep nesting, noisy comments, or inconsistent naming
- A feature is complete and you want a maintainability pass before formal review
- You want one focused simplification pass, not a multi-agent review workflow
Do not use this skill for:
- Behavior changes, feature work, or bug fixes that alter requirements
- Large architectural redesigns across untouched modules
- Spec alignment review, security review, or performance review
- Three-reviewer cleanup workflows; use
simplifyfor that
Workflow
1. Define the Scope
- Use user-specified files or ranges if provided
- Otherwise inspect recent changes with
git diff,git diff --name-only, orgit status - Default to touched code only; do not expand into unrelated cleanup
2. Read Local Standards
- Check project instructions first such as
AGENTS.md, local skill rules, and repo conventions - Follow existing naming, formatting, and structure in the touched files
- If local conventions conflict with generic cleanup preferences, local conventions win
3. Simplify Without Changing Semantics
- Reduce unnecessary nesting
- Remove duplication that is truly local and obvious
- Rename variables or helpers only when clarity improves and the rename is safe
- Prefer straightforward control flow over dense one-liners
- Avoid nested ternaries; use
if/elseorswitchfor multi-branch logic - Remove comments that only restate the code; keep comments that explain intent or constraints
- Preserve helpful abstractions; do not flatten structure just to reduce line count
4. Guardrails
- Do not add features, options, or speculative generalization
- Do not broaden API surface or change data contracts
- Do not rewrite untouched modules for style consistency alone
- Do not claim "no behavior change" without verification
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 82 lines · 41 tokens per session scan A ed457e7613cc
code-simplifier is a skill published in the GitHub repository ValorVie/custom-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 742 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-31.
Other skills, from other repositories
bug-report
Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
security-audit
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
engineering-wisdom
Provide an explicitly requested, repository-grounded engineering review using contextual heuristics for code clarity, SOLID and design, testing, refactoring, architecture, and professional practice. Use only when the user invokes $engineering-wisdom or explicitly asks for this installed engineering-wisdom pack; do not…
webiny-admin-website-builder-catalog
Name: $addElementReferenceToParent Import: import { $addElementReferenceToParent } from "webiny/admin/website-builder/page/editor" Source: @webiny/app-website-builder/editorSdk/utils/index.ts.