clean

A code-cleanup workflow that formats files, sorts imports, fixes lint errors, and resolves type-checking problems across a codebase.

In plain words
What is it for?
Use it with Python, JavaScript, or TypeScript projects to run tools such as Black, isort, Prettier, ESLint, and TypeScript checks, then review the edits.
Why use it?
It removes inconsistent style and common quality issues that make code harder to read or cause automated checks to fail.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/steipete/agent-rules/clean
Clone the repo
git clone --depth 1 https://github.com/steipete/agent-rules
Per session 269 This file is loaded in full into every session.
When invoked 269 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00269 $0.00269
Opus 5 $0.00134 $0.00134
Sonnet 5 $0.00054 $0.00054
Haiku 4.5 $0.00027 $0.00027

Measured yesterday against content hash 79f9807849ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • clean — 100% identical, 0 lines differ
project-rules/clean.mdc · 35 lines

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:

  1. Format with Black: black .
  2. Sort imports with isort: isort .
  3. Fix flake8 issues: flake8 . --extend-ignore=E203
  4. Resolve mypy type errors: mypy .

JavaScript/TypeScript Projects:

Fix all ESLint, Prettier, and TypeScript issues

Steps:

  1. Format with Prettier: npx prettier --write .
  2. Fix ESLint issues: npx eslint . --fix
  3. Check TypeScript: npx tsc --noEmit

General Process:

  1. Run automated formatters first
  2. Fix remaining linting issues manually
  3. Resolve type checking errors
  4. Verify all tools pass with no errors
  5. 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
Changes

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.

  1. yesterday First seen · 35 lines · 269 tokens per session scan A 79f9807849ea

Subscribe to this mod's changes

clean is a cursor rule published in the GitHub repository steipete/agent-rules (5,696 stars, last pushed 4mo ago), licensed MIT. It adds 269 tokens to every session, about $0.0013 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.