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/csabakovacs/rulesmith/code-simplifiernpx skills add CsabaKovacs/rulesmith --skill code-simplifiergit clone --depth 1 https://github.com/CsabaKovacs/rulesmithWhat 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.00028 | $0.00614 |
| Opus 5 | $0.00014 | $0.00307 |
| Sonnet 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 yesterday.
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.
- yesterday 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 4mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 614 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…