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.
git clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkitWrote 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/stefan-jansen/claude-code-toolkit/index)<a href="https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/index"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/index/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/index"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/index.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00008 | $0.00388 |
| Opus 5.5 | $0.00003 | $0.00155 |
| Sonnet 5.5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
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 1mo 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
Index Project
Create persistent project understanding that survives sessions.
Input: $ARGUMENTS
Modes
- (no args): Full project scan
--update: Incremental changes only--refresh: Complete regeneration"focus area": Targeted analysis
Process
-
Analyze Structure
- Detect language (Python/JS/TS/Go)
- Identify frameworks (Django, React, FastAPI, etc.)
- Map directories: src/, lib/, tests/, docs/
- Find entry points: main.py, index.js, app.py
-
Generate PROJECT_MAP.md
# Project Map: [Name] ## Quick Overview - Type: [web app/library/service] - Language: [primary] - Frameworks: [detected] ## Directory Structure - `src/` - Main application - `tests/` - Test files ## Key Files - `main.py` - Entry point - `config.yaml` - Configuration ## Patterns - Architecture: [pattern] - Testing: [approach] -
Auto-import to CLAUDE.md
- Add
@.claude/PROJECT_MAP.mdimport - Create CLAUDE.md if doesn't exist
- Add
Output
.claude/PROJECT_MAP.md- Project understanding- CLAUDE.md updated with import
Benefits
/analyzehas persistent context/explorestarts with project knowledge- New sessions understand codebase immediately
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.
- 1mo ago First seen · 64 lines · 8 tokens per session scan A 1031a6b719a3
index is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (90 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 388 once invoked, about $0.0000 per session on Opus 5.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
ctx
Search agent history or trace code to its original agent session.
context-stats
Display context window usage and token statistics.
learn
A command for recording lessons learned from direct notes, recent errors, or the current work session. It can classify lessons, suggest automations from git history, and manage the saved list.
handoff
Write a session handoff document for continuity.
revise-claude-md
Update CLAUDE.md with learnings from this session.
session-save
Save the current session state — decisions, modified files, current status, and next steps — to a handoff file for later resume.