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.
npx agentmods add rules/raysalem/real_estate_sd_web_scraper/maintenancegit clone --depth 1 https://github.com/raysalem/real_estate_sd_web_scraperWrote 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/raysalem/real_estate_sd_web_scraper/maintenance)<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="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 | $0.00000 | $0.00319 |
| Opus 5 | $0.00000 | $0.00160 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 3d 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.
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.mdwhich 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.mdinstead of acting on it. - Clean Documentation: Ensure that all legacy areas you touch are documented in
docs/detailed.md.
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.
- 3d ago First seen · 22 lines · 319 tokens per session scan A 53c04406960c
maintenance is a cursor rule published in the GitHub repository raysalem/real_estate_sd_web_scraper (2 stars, last pushed 6mo 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.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.