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 skills add saski/arnesto --skill code-simplifiergit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/code-simplifier)<a href="https://agentmods.dev/skills/saski/arnesto/code-simplifier"><img src="https://agentmods.dev/badge/skills/saski/arnesto/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/skills/saski/arnesto/code-simplifier"><img src="https://agentmods.dev/badge/skills/saski/arnesto/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.00040 | $0.00464 |
| Opus 5.5 | $0.00016 | $0.00186 |
| Sonnet 5.5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
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 1mo 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.
What it actually says
STARTER_CHARACTER = 🧹
When starting, announce: "🧹 Using CODE-SIMPLIFIER skill".
Scope
Default scope: code modified in the current session or specified by the user. Broader scope only when explicitly requested.
Read CLAUDE.md for project-specific coding standards before making changes.
Process
- Identify the code sections in scope
- Analyze each section for simplification opportunities
- Apply changes one at a time — run tests if available to verify behavior preservation
- Summarize what changed and why
Simplification Principles
Prioritize clarity over brevity.
- Reduce nesting depth — extract early returns, guard clauses
- Eliminate dead code, unreachable branches, unused variables
- Replace complex conditionals with named booleans or extracted functions
- Consolidate duplicated logic only when the duplication is real (same reason to change), not coincidental
- Remove comments that restate what the code already says
- Flatten callback chains or deeply nested structures
- Use domain language in names — describe what things ARE, not implementation details
Over-Simplification Anti-Patterns
These make code worse, not better. Do not apply them:
- Nested ternaries: Use if/else or switch for multiple conditions
- Dense one-liners: A readable 3-line version beats a clever 1-line version
- Premature abstraction: Three similar lines are better than a generic helper used once
- Merging unrelated concerns: Two simple functions beat one "smart" function with flags
- Stripping useful abstractions: If an abstraction improves organization or testability, keep it
- Compressing at the cost of debuggability: Code that's hard to step through with a debugger is too compressed
What NOT to Change
- Test code (unless imports/names must follow production renames)
- Public API signatures (unless explicitly requested)
- Behavior — the code must do exactly what it did before
- Code outside of scope
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.
- 1mo ago First seen · 53 lines · 40 tokens per session scan A cca806d2c549
code-simplifier is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed yesterday), licensed Unlicense. It adds 40 tokens to every session and 464 once invoked, about $0.0002 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-31.
Other skills, from other repositories
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
repo-harness-assessment
Use when evaluating repository agent-readiness, mapping harness roles, choosing the next smallest improvement, or designing and reconciling agent entrypoints such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, or GitHub instructions.
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
validation-harness-design
Use when designing repository validation commands, doctor scripts, test matrices, JSON or JUnit outputs, CI gates, smoke checks, or harness command surfaces.