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/openshift/rosa/30-docs-and-reviewgit clone --depth 1 https://github.com/openshift/rosaWhat 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.00239 |
| Opus 5 | $0.00000 | $0.00120 |
| Sonnet 5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
30-docs-and-review 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 2d 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
Docs And Review
- Keep repo-local agent guidance centered in
AGENTS.md; tool-specific files should point back to it instead of duplicating policy. - Keep contributor workflow text aligned with
CONTRIBUTING.md, current hook behavior, realMakefiletargets, and the docs indexed fromAGENTS.md. - Keep PR and issue templates specific, reproducible, and grounded in real ROSA workflows.
- For AWS-facing setup, troubleshooting, or architecture wording, cross-check official ROSA and AWS docs linked from
AGENTS.md. - Keep
CLAUDE.mdthin and Claude-specific; use@AGENTS.mdfor shared guidance instead of restating repo policy there. - Do not invent product behavior, architecture support, or setup prerequisites when the documentation already defines them.
- Favor concise, stable instructions over long generic AI boilerplate.
- When reviewing docs, flag outdated commands, stale file paths, placeholder Jira URLs, or wording that no longer matches the repo's actual workflow.
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.
- 2d ago First seen · 17 lines · 0 tokens per session scan A 85ee0d5bf19e
30-docs-and-review is a cursor rule published in the GitHub repository openshift/rosa (103 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 239 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-30.
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.