A set of rules for safely changing existing, messy, or high-risk codebases. It focuses on keeping changes small, isolated, and checked for regressions.

It helps fix bugs or add features while checking dependent code, documenting risks, making incremental changes, and recording out-of-scope cleanup work.

It limits accidental breakage and prevents unrelated refactoring from expanding the task.

maintenance — Cursor rule for Cursor by raysalem

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.

Clone the repo

git clone --depth 1 https://github.com/raysalem/real_estate_sd_web_scraper

Made for: Cursor.

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

README.md

[![agentmods](https://agentmods.dev/badge/rules/raysalem/real_estate_sd_web_scraper/maintenance/github.svg)](https://agentmods.dev/rules/raysalem/real_estate_sd_web_scraper/maintenance)

Your own site

<a href="https://agentmods.dev/rules/raysalem/real_estate_sd_web_scraper/maintenance"><img src="https://agentmods.dev/badge/rules/raysalem/real_estate_sd_web_scraper/maintenance/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/raysalem/real_estate_sd_web_scraper/maintenance"><img src="https://agentmods.dev/badge/rules/raysalem/real_estate_sd_web_scraper/maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 319 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00319
Opus 5.5	$0.00000	$0.00128
Sonnet 5.5	$0.00000	$0.00064
Haiku 4.5	$0.00000	$0.00032

Measured 2mo ago against content hash 53c04406960c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

maintenance 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 2mo 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.

.cursor/rules/maintenance.mdc · 22 lines

What it actually says

Brown Zone Maintenance

In "Brown Zone" projects (existing, messy, or high-risk codebases), the AI must adopt a "Leave it better than you found it" approach:

1. Principles

Strict Isolation: When fixing a bug or adding a feature, isolate changes to prevent cascading failures.
Micro-Refactoring: Identify and clean up small amounts of technical debt only in the immediate area of your changes. Do not perform global refactors unless explicitly asked.
Impact Analysis: Before modifying a shared utility or base class, search the entire repo to identify all dependent modules.

2. Risk Mitigation

Identify Affected Areas: Specifically document in docs/plan.md which legacy features might be at risk.
Pre-Implementation Check: Before modifying, read related legacy code to ensure you understand side-effects.
Incremental Changes: Prefer small, atomic commits/changes over large, sweeping updates.
Zero Regression Policy: The Judicial Review MUST include a regression check for all identified high-risk areas.

3. Slop Control

No Refactor Creep: If you see a major refactoring opportunity outside the scope of the current prompt, add it to docs/todo.md instead of acting on it.
Clean Documentation: Ensure that all legacy areas you touch are documented in docs/detailed.md.

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.

2mo ago First seen · 22 lines · 319 tokens per session scan A 53c04406960c

Subscribe to this mod's changes

maintenance is a cursor rule published in the GitHub repository raysalem/real_estate_sd_web_scraper (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 319 tokens. 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.

Code review

maintenance

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Brown Zone Maintenance

1. Principles

2. Risk Mitigation

3. Slop Control

What this file has done since we first saw it

Other cursor rules, from other repositories

clean-code-reviewer

sweep-benchmarks

code-review

ponytail

angular-20

dev-standard