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.
git clone --depth 1 https://github.com/ckorhonen/claude-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/commands/ckorhonen/claude-skills/simplify)<a href="https://agentmods.dev/commands/ckorhonen/claude-skills/simplify"><img src="https://agentmods.dev/badge/commands/ckorhonen/claude-skills/simplify/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/commands/ckorhonen/claude-skills/simplify"><img src="https://agentmods.dev/badge/commands/ckorhonen/claude-skills/simplify.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.00019 | $0.00703 |
| Opus 5.5 | $0.00008 | $0.00281 |
| Sonnet 5.5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
simplify 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.
This is a copy
97% identical to code-simplifier — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplifier
Simplify code after implementation. Find ways to make code cleaner and simpler without changing behavior.
Philosophy
- Simpler is better
- Less code = fewer bugs
- Clarity over cleverness
- Don't change behavior, only structure
- Delete code when possible
Phase 1: Identify Recent Changes
git diff HEAD~1 --name-only
git log -1 --stat
git diff HEAD~1
Phase 2: Analyze for Simplification
Look for these patterns:
1. Duplicate Code
- Repeated logic that can be extracted
- Similar functions that can be merged
- Copy-pasted code with minor variations
2. Over-Engineering
- Abstractions used only once
- Unnecessary wrapper functions
- Over-parameterized functions (too many options)
- Premature generalization
3. Dead Code
- Unused variables
- Unreachable branches
- Commented-out code
- Unused imports/dependencies
4. Complex Conditionals
- Nested if-else chains (flatten with early returns)
- Complex boolean expressions (extract to named variables)
- Guard clauses that can be simplified
5. Long Functions
- Functions > 20 lines (consider splitting)
- Multiple responsibilities (single responsibility)
- Too many parameters (use objects)
6. Unnecessary Complexity
- Try-catch around code that can't fail
- Null checks on values that can't be null
- Defensive code for impossible cases
Phase 3: Propose Simplifications
For each finding, present:
### Simplification: [Short description]
**Location**: `file:line`
**Type**: [Duplicate/Over-engineering/Dead code/etc.]
**Current** (X lines):
```[lang]
[code block]
Simplified (Y lines):
[code block]
Benefit: [Why this is better] Risk: Low - behavior unchanged
## Phase 4: Apply Simplifications
After user approval:
1. Make one change at a time
2. Run tests after each change
3. Commit with clear message: `refactor: simplify [description]`
4. Move to next simplification
## Output Format
Simplification Report
Changes Analyzed
- Files: [count]
- Lines added: [count]
- Lines removed: [count]
Simplification Opportunities
[List each opportunity with current/simplified code]
Summary
- Simplifications found: X
- Estimated lines reducible: Y
- Complexity reduction: [High/Medium/Low]
Recommended Actions
- Apply simplification #1 (highest impact)
- Apply simplification #2 ...
Tests to Run After
- [List of test commands to verify no behavior change]
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 · 143 lines · 19 tokens per session scan A 6b10eaae6717
simplify is a command published in the GitHub repository ckorhonen/claude-skills (22 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 703 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to code-simplifier, differing in 14 lines, and is treated as a copy.
Other commands, from other repositories
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
multi-review
Multi-agent code review with diverse perspectives - run multiple specialized reviewers in parallel for comprehensive analysis.
parallel-cleanup
Run a fresh-context parallel cleanup review of the current work.
vibe-check
Audit a vibe-coded app across the six things that actually block shipping, and get a prioritized fix list.
address-pr-comments
Triage and address PR comments from code review bots - analyzes feedback, prioritizes issues, fixes valid concerns, and declines incorrect suggestions.
review-loop
Review/fix loop until clean.