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/iliaal/codesage/codesage-reindexgit clone --depth 1 https://github.com/iliaal/codesageWrote 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/commands/iliaal/codesage/codesage-reindex)<a href="https://agentmods.dev/commands/iliaal/codesage/codesage-reindex"><img src="https://agentmods.dev/badge/commands/iliaal/codesage/codesage-reindex.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00754 |
| Opus 5 | $0.00016 | $0.00377 |
| Sonnet 5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
codesage-reindex 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Force incremental CodeSage re-index
Wraps codesage index for cases when you want an immediate refresh without waiting for a commit/merge/checkout hook. If the project's config.toml embedding model no longer matches the active model in the DB, the script detects this and runs codesage cleanup first to drop orphan vec tables from the previous model.
Step 1: Resolve the target project
$ARGUMENTS is the project path. If empty, use the current working directory. Verify it has .codesage/index.db — if not, tell the user to run /codesage-onboard <path> first and stop.
Step 2: Detect model mismatch
Run a dry-run cleanup to detect orphan vec tables left behind from a previous model:
cd <project> && codesage cleanup --dry-run
Output format:
Active model:andActive table:header lines reflect whatconfig.tomlcurrently says- One
keep:line per table that matches the active model - One
DRY-RUN drop:line per orphan table from a previous model
If any DRY-RUN drop: lines appear, the user switched models in config.toml without wiping the DB. Run the real cleanup:
cd <project> && codesage cleanup
Report which tables were dropped and the DB size reclaimed.
If the dry-run shows only keep: lines, skip the cleanup step entirely — no output, no narration.
Step 3: Pre-count
cd <project> && codesage status
Capture the chunk count so you can report the delta after reindexing.
Step 4: Incremental index
cd <project> && codesage index
Incremental — only changed files get re-processed. On a warm GPU with no changes it's under 5 seconds. On a large delta, minutes.
If the command runs over ~30 seconds, background it and poll.
If the mismatch path ran, the semantic portion will rebuild from scratch for everything (because the cleanup dropped the vec tables). Warn the user up front that this pass is doing real work, not a cheap incremental.
Step 5: Report
Parse the codesage index output. It prints these lines:
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.
- 5d ago First seen · 77 lines · 33 tokens per session scan A 475167c1d806
codesage-reindex is a command published in the GitHub repository iliaal/codesage (20 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 754 once invoked, about $0.0002 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
rb-setup
First-time setup. Configure the LLM API key, or a no-API-key local host runner (Codex / Trae / Claude / any headless CLI) that RepoBrain uses for codebase Q&A and refresh. / 首次 setup，配置 RepoBrain 代码问答与 refresh 所需的 LLM API key，或无需 API key 的本地 host runner（Codex / Trae / Claude / 任意无头 CLI）。.
rb-ask
Ask a question about the current project's codebase via the repobrain knowledge hub. / 通过 repobrain 知识库询问当前项目代码。.
rb-refresh
Rebuild the repobrain project knowledge base after significant changes. / 在重要改动后重建 repobrain 项目知识库。.
rb-init
Scaffold a new multi-agent repository from the RepoBrain template (invokes agent-repo-init skill). / 基于 RepoBrain 模板创建新的多智能体仓库。.
rp-build-cli
Build with rp-cli context builder → chat → implement.
rp-investigate-cli
Deep codebase investigation and architecture research with rp-cli commands.