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/hypershift/code-reviewgit clone --depth 1 https://github.com/openshift/hypershiftWhat 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.00003 | $0.00226 |
| Opus 5 | $0.00002 | $0.00113 |
| Sonnet 5 | $0.00001 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
code-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 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
Prior to submitting or pushing code to Github, these steps should be reviewed
Reviewing the introduced changes
- Use the rules described at https://hypershift.pages.dev/contribute/#prior-to-submitting-a-pull-request to analyze the code changes.
Generate a mermaid diagram with the introduced code
- if you add enumerations, remove the . and change them to -
- Always in english
- Avoid using {} or () in the names
Generate a commit message according the code changed in the PR:
- All commit messages should follow the format outlined in the @git-commit-format.mdc rule.
Basic Rules
- If a code change does not make any sense, please call that out
- Don't provide reasoning without supporting evidence
100-go-mistakes rules taken from https://100go.co/
- Follow the @100-go-mistakes.mdc rules
How code should be scoped
- Follow the documentation at https://hypershift.pages.dev/contribute/.
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 · 27 lines · 3 tokens per session scan A a3f06a80c1ea
code-review is a cursor rule published in the GitHub repository openshift/hypershift (538 stars, last pushed yesterday), licensed Apache-2.0. It adds 3 tokens to every session and 226 once invoked, about $0.0000 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-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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.