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-resetgit clone --depth 1 https://github.com/iliaal/codesageWhat 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.00027 | $0.00870 |
| Opus 5 | $0.00014 | $0.00435 |
| Sonnet 5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
codesage-reset 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reset and rebuild a CodeSage index
Drops .codesage/index.db and performs a full re-index. Use after:
- Editing
.codesage/config.tomlin a way that breaks the existing index (model switch, pooling change) - Switching embedding device (CPU ↔ GPU — embeddings produced on different devices are not bit-identical)
- Index corruption or weird state
- Upgrading CodeSage to a version with incompatible storage
For routine refresh use /codesage-reindex. Reset is destructive and pays the full embedding cost.
Before touching any
.codesage/path:.codesage/is repository content, so a cloned repo can ship it — or any directory under it — as a symlink. Refuse to read, write, create, or delete through one. Check withtest -L <path>(nottest -e, which follows links) on.codesageitself and on each subdirectory you are about to use, and stop with an error if any is a symlink. Apply the same check to every leaf you touch: a*.jsonfindings file, or any temporary file you create beside it, may itself be a planted symlink or a directory. Read or write a leaf only if it is a regular file (or absent, when creating), and give temporary files a freshly generated unique name rather than a predictable one.
Step 1: Resolve and confirm
$ARGUMENTS — project path (default cwd). Verify it has .codesage/index.db; if not, stop and tell the user to run /codesage-onboard first.
Before touching anything, confirm with the user: "About to reset CodeSage index for <project>. This deletes .codesage/index.db and rebuilds from scratch — on CUDA this typically takes under a few minutes for most repos. Proceed?" Wait for explicit yes.
Skip confirmation only if --yes is in $ARGUMENTS.
Step 2: Capture pre-reset state
cd <project> && codesage status
Record chunk count and file count. This is the baseline for the post-reset diff. codesage status does not emit a language breakdown; run codesage overview if you want one.
Step 3: Drop the index
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 · 76 lines · 27 tokens per session scan A d9fed4c81186
codesage-reset is a command published in the GitHub repository iliaal/codesage (20 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 870 once invoked, about $0.0001 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.