Borrowing it
Nothing to install: this file belongs to CsabaKovacs/rulesmith. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CsabaKovacs/rulesmith/main/.agents/skills/code-simplifier/SKILL.mdgit clone --depth 1 https://github.com/CsabaKovacs/rulesmithWrote 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/csabakovacs/rulesmith/code-simplifier)<a href="https://agentmods.dev/skills/csabakovacs/rulesmith/code-simplifier"><img src="https://agentmods.dev/badge/skills/csabakovacs/rulesmith/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/csabakovacs/rulesmith/code-simplifier"><img src="https://agentmods.dev/badge/skills/csabakovacs/rulesmith/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.00028 | $0.00614 |
| Opus 5.5 | $0.00011 | $0.00246 |
| Sonnet 5.5 | $0.00006 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplifier
Simplifies recently changed code for clarity and maintainability while preserving external behavior.
When to Activate
- After code modifications that introduce new logic, refactor existing code, or add significant complexity.
- Skip for trivial changes, deletions-only, config changes, or documentation edits.
Simplification Methodology
Follow these steps in order:
- Identify recently changed functions, classes, and modules.
- Look for unnecessarily verbose control flow that can be simplified.
- Find repeated patterns that can be consolidated (only when 3+ concrete occurrences exist).
- Check for over-abstraction: remove indirection layers that do not add value.
- Check for under-abstraction: consolidate duplicated logic into focused helpers when repetition is proven.
- Simplify deeply nested code by extracting guard clauses and early returns.
- Verify that every proposed simplification preserves identical external behavior.
- Prefer clarity over cleverness — readable code beats short code.
- Do NOT rename broadly; only rename within the touched scope when it meaningfully improves readability.
- Apply changes directly — this agent modifies code, unlike review-only agents.
Stack-Specific Simplification Rules
- Replace verbose promise chains with async/await where it improves readability. (evidence: packages/core/src/scanner/index.ts)
- Consolidate repeated type assertions into a single type guard function. (evidence: packages/core/src/render/rulebook.ts)
- Prefer
Array.method()chains over manual for-loops when intent is clearer. (evidence: packages/core/src/scanner/index.ts) - Flatten deeply nested
if/switchin AST visitors into early-return guard clauses. (evidence: packages/core/src/render/ast.ts)
Project Conventions to Preserve
- Module-level functions, no class wrappers.
Record<string, unknown>for JSON, neverany. - Constants: UPPER_SNAKE_CASE. Functions: camelCase. Types: PascalCase.
.jsextensions in imports. File I/O throughsafe.tsonly.- Private helpers are unexported module-scoped functions.
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 · 66 lines · 28 tokens per session scan A 0c6dbc5ee650
code-simplifier is a skill published in the GitHub repository CsabaKovacs/rulesmith (15 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 614 once invoked, about $0.0001 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-30.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…