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/d3x293/code-crew/crew-reindexgit clone --depth 1 https://github.com/d3x293/code-crewWhat 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.00022 | $0.00145 |
| Opus 5 | $0.00011 | $0.00072 |
| Sonnet 5 | $0.00004 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
crew-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 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
Invoke the codecrew:codebase-index skill in full-rebuild mode.
This will:
- Re-scan all source files in the project
- Rebuild Layer 1 (compact index) with fresh hashes, summaries, exports
- Rebuild Layer 2 (symbol map) with function signatures, call graph, line ranges
- Report what changed since last index
Use this when:
- Index feels stale or agents are finding wrong files
- After major refactors that moved/renamed many files
- After pulling large changes from git
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 · 17 lines · 22 tokens per session scan A f4c8c771a722
crew-reindex is a command published in the GitHub repository d3x293/code-crew (13 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 145 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
plugin-audit
Run the full 8-phase plugin audit pipeline on a skill directory.
update-docs
Update all the documentation related files.
focused-fix
Deep-dive feature repair — systematically fix an entire feature/module. Usage: /focused-fix.
ask
Consult a craft agent. Routes your question to the best mind in the workshop - not a menu, a recommendation.
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
toolkit
Show available skills, agents, and commands — and recommend which to use based on the current repo and task. Helps new users discover what capabilities are available.