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.
git clone --depth 1 https://github.com/marjoballabani/hypergrepWrote 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/marjoballabani/hypergrep/cursorrules)<a href="https://agentmods.dev/rules/marjoballabani/hypergrep/cursorrules"><img src="https://agentmods.dev/badge/rules/marjoballabani/hypergrep/cursorrules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/marjoballabani/hypergrep/cursorrules"><img src="https://agentmods.dev/badge/rules/marjoballabani/hypergrep/cursorrules.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00414 | $0.00414 |
| Opus 5.5 | $0.00166 | $0.00166 |
| Sonnet 5.5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
cursorrules 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 1mo 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
This project has hypergrep installed globally. Use it instead of grep/ripgrep when you need structural understanding of code (function bodies, call graphs, impact analysis). For simple text searches, ripgrep is fine.
When to use hypergrep vs ripgrep:
- Quick text search ->
rg "pattern" .(faster for one-off) - Find + understand a function ->
hypergrep -s "function" . - Search with token budget ->
hypergrep --layer 1 --budget 800 --json "pattern" . - Who calls this / what breaks ->
hypergrep --callers/--impact - Does project use X ->
hypergrep --exists "redis" . - Codebase overview ->
hypergrep --model "" .
Session start:
hypergrep --model "" .-- understand the codebase (run once)hypergrep-daemon --background .-- optional, start if making 10+ searches (auto-stops after 30 min)
Commands:
hypergrep --layer 1 --budget 800 --json "pattern" .-- signatures + call graph in 800 tokenshypergrep -s "pattern" .-- full function bodies (to edit)hypergrep --callers "function_name" .-- who calls this?hypergrep --callees "function_name" .-- what does this call?hypergrep --impact "function_name" .-- what breaks? (run before editing)hypergrep --exists "redis" .-- technology check (NO = guaranteed, YES = likely)
Rules:
- Run
hypergrep --model "" .at session start - Use hypergrep when you need to understand code, rg when you just need to find text
- Run
hypergrep --impactbefore changing any function - Use
hypergrep -sinstead of reading whole files for specific functions
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.
- 1mo ago First seen · 28 lines · 414 tokens per session scan A 602e1ef27231
cursorrules is a cursor rule published in the GitHub repository marjoballabani/hypergrep (24 stars, last pushed 6mo ago), licensed MIT. It adds 414 tokens to every session, about $0.0017 per session on Opus 5.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
fix
Auto-fix archguardian findings like unused imports and naming violations.
architecture
agent-inspect architecture and product context.
hatch3r-observability-logging
Structured logging and error reporting conventions for the project.
agents-tier-system
../../.agents/rules/agents-tier-system.md.
consumer-surfaces
../../.agents/rules/consumer-surfaces.md.
docs-governance
../../.agents/rules/docs-governance.md.