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/ivangrynenko/cursorrules/readme-maintenance-standardsgit clone --depth 1 https://github.com/ivangrynenko/cursorrulesWrote 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/ivangrynenko/cursorrules/readme-maintenance-standards)<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/readme-maintenance-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/readme-maintenance-standards.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.00714 |
| Opus 5 | $0.00000 | $0.00357 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
readme-maintenance-standards 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- readme-maintenance-standards — 100% identical, 0 lines differ
What it actually says
Enhanced README Maintenance Standards
Ensures that README files are consistently maintained, up-to-date, and informative.
actions:
-
type: enforce conditions:
-
pattern: "## (Available Rules|Features|Components)" message: "Update the 'Available Rules/Features/Components' section whenever new elements are added."
-
pattern: "\[
[^]+`\]\([^)]+\)" message: "Ensure all file references in the README are properly linked and point to existing files." -
pattern: "## (Installation|Usage|Configuration)" message: "Keep setup, usage, and configuration sections current with the latest project changes."
-
pattern: "## (Contributing|License)" message: "Ensure contributing guidelines and license information are accurate and up-to-date."
-
pattern: "\[Version\s*(\d+\.)?(\d+\.)?\d+\]" message: "Update version information to reflect the current state of the project."
-
pattern: "## (Changelog|Changes|Updates)" message: "Maintain a changelog for significant updates, fixes, and features."
-
-
type: suggest message: | README Maintenance Best Practices:
- Rule Listings: Automatically update or manually check if new rules or features are reflected in the README.
- Installation & Configuration: Regularly review and update installation and configuration instructions to match the latest project state.
- Documentation of Changes: Document new features, bug fixes, and changes in a changelog or dedicated section.
- Section Hierarchy: Maintain a logical structure with clear headings for easy navigation.
- Examples: Include or update examples for new or changed functionalities.
- Version Information: Keep version numbers and release notes current, linking to the changelog if applicable.
- Table of Contents: Ensure the table of contents reflects the current document structure, using auto-generated if possible.
- Badges: Update badges for CI/CD status, test coverage, or dependencies to reflect current project health.
- Accessibility: Write with accessibility in mind, using alt text for images and semantic markdown.
-
type: validate conditions:
-
pattern: "^# [^\n]+\n\n## " message: "Ensure proper markdown heading hierarchy for readability."
-
pattern: "\|[^|]+\|[^|]+\|\n\|\s*-+\s*\|" message: "Use consistent table formatting throughout the document."
-
pattern: "\[(.*?)\]\((?!http|\/)[^\)]+\)" message: "All local links should point to existing files or sections within the project."
-
pattern: "\[Version\s*(\d+\.)?(\d+\.)?\*\d+\]" message: "Check that version placeholders are updated to actual numbers before release."
-
metadata: priority: high version: 1.1
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.
- yesterday First seen · 70 lines · 0 tokens per session scan A a73e217f1333
readme-maintenance-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 714 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-09-03.
Other cursor rules, from other repositories
documentation
Documentation: code docs, READMEs, ADRs, maintenance.
document-lifecycle-guard
文档生命周期守门规则。适用于所有产品开发角色（产品经理/技术架构师/测试工程师/DevOps）激活时。规定了每个角色如何管理自己的项目文档：自建文件夹、in-place更新、追加变更记录、重大改版存旧版。禁止创建「产品定义v2.md」「新版技术架构.md」等并行版本文件。.
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
cross-tool-config
Cross-tool AI config: what transfers between Cursor, Claude Code, Copilot, Windsurf, Gemini, and Codex.
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.