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/tests-documentation-maintenancegit 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/tests-documentation-maintenance)<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/tests-documentation-maintenance"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/tests-documentation-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.00312 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
tests-documentation-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 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.
What it actually says
Tests & Documentation Maintenance
Ensures that tests are written and updated for Drupal modules and plugins, and that documentation remains current.
actions:
-
type: enforce conditions:
-
pattern: "class .*Test extends" message: "Ensure all Drupal modules and plugins have unit tests."
-
pattern: "Feature:.*" message: "Ensure front-end affecting plugins have Behat tests."
-
pattern: "function .*\(" message: "When modifying existing functionality, check and update related tests."
-
pattern: "# README" message: "Ensure README.md exists in each module and is kept up to date."
-
-
type: suggest message: | Keep tests and documentation updated:
- Write unit tests for Drupal modules and backend logic.
- Write Behat tests for plugins that affect front-end behavior.
- If functionality changes, update corresponding tests.
- Maintain a README.md file in each module and update it with relevant changes.
metadata: priority: high version: 1.0
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 · 43 lines · 312 tokens per session scan A 5a05b9214548
tests-documentation-maintenance 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 312 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
plan-tests
Design a risk-scaled test architecture for an epic before implementation begins. Produces prioritized scenarios, test level distribution, and fixture plans based on TEA and bigpowers principles.
testing-patterns
Testing patterns and best practices for PRPM codebase with Vitest.
testing-pyramid-agent
Provides guidance on testing pyramid principles and how to analyze test distribution. Use this rule when discussing test distribution, test strategy, or when analyzing test coverage across unit, integration, and E2E tests.
jest
Jest: describe/it, matchers, mocking, async testing.
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
vitest
Vitest: unit testing, mocking, coverage, snapshot testing.