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/steipete/agent-rulesWrote 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/steipete/agent-rules/clean)<a href="https://agentmods.dev/rules/steipete/agent-rules/clean"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/clean/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/rules/steipete/agent-rules/clean"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/clean.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.00269 | $0.00269 |
| Opus 5.5 | $0.00108 | $0.00108 |
| Sonnet 5.5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
clean 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- clean — 100% identical, 0 lines differ
What it actually says
Clean
Fix all code formatting and quality issues in the entire codebase.
Python Projects:
Fix all black, isort, flake8, and mypy issues
Steps:
- Format with Black:
black . - Sort imports with isort:
isort . - Fix flake8 issues:
flake8 . --extend-ignore=E203 - Resolve mypy type errors:
mypy .
JavaScript/TypeScript Projects:
Fix all ESLint, Prettier, and TypeScript issues
Steps:
- Format with Prettier:
npx prettier --write . - Fix ESLint issues:
npx eslint . --fix - Check TypeScript:
npx tsc --noEmit
General Process:
- Run automated formatters first
- Fix remaining linting issues manually
- Resolve type checking errors
- Verify all tools pass with no errors
- Review changes before committing
Common Issues:
- Import order conflicts between tools
- Line length violations
- Unused imports/variables
- Type annotation requirements
- Missing return types
- Inconsistent quotes/semicolons
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 · 35 lines · 269 tokens per session scan A 79f9807849ea
clean is a cursor rule published in the GitHub repository steipete/agent-rules (5,677 stars, last pushed 5mo ago), licensed MIT. It adds 269 tokens to every session, about $0.0011 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 cursor rules, from other repositories
lint-config
OXC and React Doctor config rationale - .oxlintrc.json options, front override, better-tailwindcss rule set, oxfmt class order and Markdown scope.
diagnose
Systematic root cause diagnosis — confidence scoring, investigation budgeting, hypothesis branching.
chaos
Failure injection mode — stress test implementations by simulating failures and hostile conditions.
incident
Production incident response — structured triage with blast radius, rollback criteria, and verification.
analyze
Codebase analysis — complexity, coupling, dead code, tech debt hotspots.
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.