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/fernandoabolafio/repobaseWrote 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/fernandoabolafio/repobase/repogrep)<a href="https://agentmods.dev/rules/fernandoabolafio/repobase/repogrep"><img src="https://agentmods.dev/badge/rules/fernandoabolafio/repobase/repogrep/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/fernandoabolafio/repobase/repogrep"><img src="https://agentmods.dev/badge/rules/fernandoabolafio/repobase/repogrep.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.00000 | $0.01879 |
| Opus 5.5 | $0.00000 | $0.00752 |
| Sonnet 5.5 | $0.00000 | $0.00376 |
| Haiku 4.5 | $0.00000 | $0.00188 |
Grade A, and why
repogrep 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.
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rule: repogrep CLI Integration
Overview
repogrep is a local code search tool that indexes repositories and provides both full-text (keyword) and semantic search capabilities. Use it to search across external codebases that have been indexed locally.
When to Use repogrep
Use repogrep when you need to:
- Search code in repositories that are NOT in the current workspace
- Find examples of patterns across multiple indexed codebases
- Explore external libraries or frameworks that have been indexed
- Read files from indexed repositories without opening them
- Perform semantic searches across large codebases
Do NOT use repogrep for:
- Searching the current workspace (use
codebase_searchorgreptools instead) - Files in the active project directory
Available Commands
1. repogrep list
List all indexed repositories to see what's available for searching.
repogrep list
Use this first to understand which repositories you can search.
2. repogrep search - Semantic & Keyword Search
The primary search command with three modes:
Keyword search (default): Fast full-text search using SQLite FTS
repogrep search "authentication middleware"
repogrep search "user login" --repo Effect-TS-effect
Semantic search: AI-powered meaning-based search
repogrep search "how to handle errors" --semantic
repogrep search "async state management" --semantic --limit 10
Hybrid search: Combines both approaches
repogrep search "database connection pooling" --hybrid
Options:
-r, --repo <name>- Filter to specific repository--semantic- Use semantic/vector search--hybrid- Combine keyword + semantic search-l, --limit <number>- Max results (default: 20)
3. repogrep grep - Pattern Search
Search for regex patterns in file contents (like ripgrep).
# Find all function declarations
repogrep grep "function \w+\(" --type ts
# Case-insensitive search with context
repogrep grep "todo" -i -C 3 --repo myproject
# Count matches per file
repogrep grep "console\.log" --type js -c
# Just show filenames
repogrep grep "deprecated" -l
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 · 244 lines · 0 tokens per session scan A 1675c9cf7964
repogrep is a cursor rule published in the GitHub repository fernandoabolafio/repobase (17 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,879 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
bootstrap-alwayson
Minimal always-required LLM fixes.
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
mcp-tools-readme
Keep README in sync when MCP tools change.
validate-design-early
Ask for design approval before implementing 100+ lines.
incremental-validation
Validate frequently and early; find errors when they're small.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.