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/panozzaj/cursor-rules/requirements-maintenancegit clone --depth 1 https://github.com/panozzaj/cursor-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/panozzaj/cursor-rules/requirements-maintenance)<a href="https://agentmods.dev/rules/panozzaj/cursor-rules/requirements-maintenance"><img src="https://agentmods.dev/badge/rules/panozzaj/cursor-rules/requirements-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.00214 | $0.00214 |
| Opus 5 | $0.00107 | $0.00107 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
requirements-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
Requirements Maintenance Rules
Requirements hold the high-level requirements for the project.
All features must be added to a well-named file in the requirements folder
Adding New Features
- Each feature must be described in detail, including its purpose and requirements
- Use subfolders of
requirementsto organize related features - Use GitHub-style checkboxes
- [ ]for all features - Place new features in the most appropriate file
- If no appropriate file exists, create a new one
- Put a descriptive comment at the top of each file (e.g. "# User Authentication Features")
Implementing Features
- Update checkbox to
- [x]when feature is fully implemented - Add implementation details as sub-items if needed
- Keep requirements synchronized with actual implementation
Validation
- Verify requirements match implemented features
- Remove or update outdated requirements
- Resolve conflicts between requirements and implementation
- Keep track of dependencies between features
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 · 33 lines · 214 tokens per session scan A 9db039123cc4
requirements-maintenance is a cursor rule published in the GitHub repository panozzaj/cursor-rules (3 stars, last pushed 1y ago), licensed MIT. It adds 214 tokens to every session, about $0.0011 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-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.