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/jstxn/reinWrote 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/rules/jstxn/rein/rein-cleanup)<a href="https://agentmods.dev/rules/jstxn/rein/rein-cleanup"><img src="https://agentmods.dev/badge/rules/jstxn/rein/rein-cleanup.svg" alt="Measured on agentmods" 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.00013 | $0.00800 |
| Opus 5 | $0.00006 | $0.00400 |
| Sonnet 5 | $0.00003 | $0.00160 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
rein-cleanup 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 8d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rein-cleanup
Reduce bloated, noisy, repetitive, or over-abstracted code with a regression-tests-first, smell-by-smell cleanup workflow that preserves behavior and raises signal quality.
When to Use
Use this skill when:
- A code path works but feels bloated, noisy, repetitive, or over-abstracted
- A user asks to "cleanup", "refactor", or "deslop" output
- Follow-up implementation left duplicate code, dead code, weak boundaries, missing tests, or unnecessary wrapper layers
- You need a disciplined cleanup workflow without broad rewrites
Scoped File Lists
- This skill can accept a file list scope instead of a whole feature area.
- When the caller provides a changed-files list, keep the cleanup strictly bounded to those files.
Procedure
-
Lock behavior with regression tests first
- Identify the behavior that must not change
- Add or run targeted regression tests before editing cleanup candidates
- If behavior is currently untested, create the narrowest test coverage needed first
-
Create a cleanup plan before code
- List the specific smells to remove
- Bound the pass to the requested files or scope
- If a file list scope is provided, keep the pass restricted to that changed-files list
- Order fixes from safest and highest-signal to riskiest
- Do not start coding until the cleanup plan is explicit
-
Categorize issues before editing
- Duplication: repeated logic, copy-paste branches, redundant helpers
- Dead code: unused code, unreachable branches, stale flags, debug leftovers
- Needless abstraction: pass-through wrappers, speculative indirection, single-use helper layers
- Boundary violations: hidden coupling, leaky responsibilities, wrong-layer imports or side effects
- Missing tests: behavior not locked, weak regression coverage, gaps around edge cases
-
Execute passes one smell at a time
- Pass 1: dead code deletion
- Pass 2: duplicate removal
- Pass 3: naming and error handling cleanup
- Pass 4: test reinforcement
- Re-run targeted verification after each pass
- Avoid bundling unrelated refactors into the same edit set
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.
- 8d ago First seen · 93 lines · 13 tokens per session scan A ab66bc9404ce
rein-cleanup is a cursor rule published in the GitHub repository jstxn/rein (12 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 800 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 cursor rules, from other repositories
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.