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/whitequeen306/code-cortex-loopWrote 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/whitequeen306/code-cortex-loop/refactor-safety)<a href="https://agentmods.dev/rules/whitequeen306/code-cortex-loop/refactor-safety"><img src="https://agentmods.dev/badge/rules/whitequeen306/code-cortex-loop/refactor-safety/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/whitequeen306/code-cortex-loop/refactor-safety"><img src="https://agentmods.dev/badge/rules/whitequeen306/code-cortex-loop/refactor-safety.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.00037 | $0.00858 |
| Opus 5.5 | $0.00015 | $0.00343 |
| Sonnet 5.5 | $0.00007 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
refactor-safety 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Safety
Apply these constraints whenever /cortexloop modifies code (Direct mode or post-Report confirmation).
Core Principles
1. Preserve Behavior Exactly
Simplification and performance changes must NOT alter:
- Inputs, outputs, or return values
- Error behavior and error messages (unless fixing a security leak)
- Side effects and their ordering
- Edge case handling
Test: If existing tests need modification to pass after a "refactor", you likely changed behavior — revert and reconsider.
2. Chesterton's Fence
Before removing or simplifying anything, understand why it exists:
- What calls this code? What does it call?
- What edge cases does it handle?
- Why was it written this way? (git blame, comments, PR history)
- Is this dead, or intentionally kept for backwards compatibility?
If you cannot answer these, do not remove or simplify — flag as UNCERTAIN in the report.
3. Ask Before Deleting
Never silently delete:
- Functions, classes, files, or exports
- Dependencies (npm/pip/cargo packages)
- Feature flags or config keys
- Error handling branches
- Comments that explain "why" (only remove "what" comments)
Use the ask-before-delete template from dead-code-and-deps skill.
4. Separate Refactors from Features
In Direct mode:
- Refactor commits/changes: simplify, rename, extract, dead code removal
- Fix commits/changes: bug fixes, security patches, test additions
- Do not mix unrelated refactors with bug fixes in the same edit group
- If a fix requires a refactor, do the fix first, verify tests, then refactor
5. Incremental Changes
- One simplification or optimization at a time
- Run tests after each change
- Revert immediately on failure — do not "fix forward" blindly
- Keep diffs reviewable — avoid 500+ line drive-by refactors
Forbidden Actions
- Empty catch blocks (even if "cleaner")
- Removing error handling to simplify code
- Disabling tests to make the pipeline pass
@ts-ignore/# noqa/allow()to silence real issues- Disabling security controls as a "fix"
- Force-pushing or rewriting git history
- Modifying lock files without running the package manager
- Major dependency version bumps without explicit user approval
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 · 108 lines · 37 tokens per session scan A b9e82cf5efd3
refactor-safety is a cursor rule published in the GitHub repository whitequeen306/code-cortex-loop (15 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 858 once invoked, about $0.0001 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
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.