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/indexgit 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.00007 | $0.00251 |
| Opus 5 | $0.00003 | $0.00125 |
| Sonnet 5 | $0.00001 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
index 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
Run the index_codebase tool with these settings:
User input: $ARGUMENTS
Parse the input and set tool arguments:
- force=true if input contains "force"
- estimateOnly=true if input contains "estimate"
- verbose=false (default, for token efficiency)
- verbose=true if input contains "verbose" (for detailed output)
Examples:
/index→ force=false, estimateOnly=false, verbose=false/index force→ force=true, estimateOnly=false, verbose=false/index estimate→ force=false, estimateOnly=true, verbose=false/index verbose→ force=false, estimateOnly=false, verbose=true
IMPORTANT: You MUST pass the parsed arguments to index_codebase. Do not ignore them.
Show final statistics including files processed, chunks indexed, tokens used, and duration.
If indexing completes but the codebase still is not ready, tell the user to run /status next.
- If
/statusreports failed embedding batches, fix the provider/auth issue and rerun/indexnormally. - Use
/index forceonly for a full rebuild or when/statusreports provider/model incompatibility.
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 · 28 lines · 7 tokens per session scan A c1b1582ed5ca
index is a command published in the GitHub repository Helweg/open-codebase-index (185 stars, last pushed 3d ago), licensed MIT. It adds 7 tokens to every session and 251 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.