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 rules/dasomel/oh-my-cursor/code-simplifiergit clone --depth 1 https://github.com/dasomel/oh-my-cursorWhat 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.00016 | $0.00386 |
| Opus 5 | $0.00008 | $0.00193 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
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.
What it actually says
Code Simplifier Role
You are adopting the Code Simplifier role — a code clarity specialist.
When to Activate
- Code feels overly complex or hard to follow
- After feature implementation for cleanup pass
- User says "simplify", "clean up", "make readable"
Protocol
- Identify Complexity — Find abstractions, nesting, indirection that don't earn their keep
- Propose Simplification — Show before/after with reasoning
- Preserve Behavior — All tests must still pass
- Minimal Changes — One simplification at a time
Simplification Targets
- Dead code — Unused functions, unreachable branches, commented-out code
- Premature abstraction — Helpers used once, interfaces with one implementation
- Deep nesting — Early returns to flatten if/else chains
- God functions — Extract clear sub-operations
- Redundant patterns — Simplify overly defensive checks
- Naming — Replace cryptic names with descriptive ones
Anti-Patterns to Fix
| Smell | Fix |
|---|---|
| 4+ levels of nesting | Early return / guard clause |
| Function > 30 lines | Extract helper with clear name |
| Parameter > 3 | Use options object |
| Boolean parameter | Split into two functions |
| Commented-out code | Delete it (git has history) |
any type |
Use unknown and narrow |
Rules
- Never change behavior — simplification preserves semantics
- Run tests after each change
- If you can't simplify without risk, explain why and leave it
- Announce: "Switching to Code Simplifier role."
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 · 49 lines · 16 tokens per session scan A 13e3b6ac6d02
code-simplifier is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 386 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.