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 commands/helweg/open-codebase-index/searchgit clone --depth 1 https://github.com/Helweg/open-codebase-indexWhat 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.00008 | $0.00344 |
| Opus 5 | $0.00004 | $0.00172 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
search 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
Search the codebase using semantic search.
User input: $ARGUMENTS
The first part is the search query. Look for optional parameters:
limit=Nor "top N" or "first N" → set limittype=Xor mentions "functions"/"classes"/"methods" → set chunkTypedir=Xor "in folder X" → set directory filter- File extensions like ".ts", "typescript", ".py" → set fileType
author=XorblameAuthor=X→ set blameAuthor filtersha=XorblameSha=X→ set blameSha filtersince=YYYY-MM-DDorblameSince=YYYY-MM-DD→ set blameSince filteruntil=YYYY-MM-DDorblameUntil=YYYY-MM-DD→ set blameUntil filter
Call codebase_search with the parsed arguments.
Examples:
/search authentication logic→ query="authentication logic"/search error handling limit=5→ query="error handling", limit=5/search validation functions→ query="validation", chunkType="function"/search auth logic [email protected] since=2025-01-01 until=2025-01-31→ query="auth logic", blameAuthor="[email protected]", blameSince="2025-01-01", blameUntil="2025-01-31"
If the index doesn't exist, run index_codebase first.
Return results with file paths and line numbers.
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 · 30 lines · 8 tokens per session scan A 65bfe1363580
search is a command published in the GitHub repository Helweg/open-codebase-index (185 stars, last pushed 3d ago), licensed MIT. It adds 8 tokens to every session and 344 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 commands, from other repositories
rp-build-cli
Build with rp-cli context builder → chat → implement.
rp-investigate-cli
Deep codebase investigation and architecture research with rp-cli commands.
rp-oracle-export-cli
Export context for oracle consultation using rp-cli.
rp-reminder-cli
Continue your current workflow using rp-cli instead of built-in alternatives.
merge
Land the current feature branch on develop — README/CHANGELOG checks, commit, push, PR, auto-merge.
codesage-review
Review CodeSage feature slices in parallel and persist validated findings.