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/stefan-jansen/claude-code-toolkit/setup-statuslinegit clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkitWhat 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.00009 | $0.00193 |
| Opus 5 | $0.00005 | $0.00097 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
setup:statusline 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
Statusline Configuration
I'll configure the Claude Code statusline to display framework context.
echo "🎨 Configuring Claude Code statusline..."
echo ""
# Configure statusline via Claude Code settings
# This would typically integrate with Claude Code's statusline API
# For now, provide guidance
echo "To configure the statusline:"
echo ""
echo "1. Add to your user settings (~/.config/claude-code/settings.json):"
echo ' "statusline": {'
echo ' "showFramework": true,'
echo ' "showWorkUnit": true,'
echo ' "showMemoryFiles": true'
echo ' }'
echo ""
echo "2. Or configure per-project in .claude/settings.json"
echo ""
echo "✅ Statusline configuration guidance provided"
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 · 32 lines · 9 tokens per session scan A d4875da138f0
setup:statusline is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (85 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 193 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
remember
Save something to agent memory - picks project or user scope automatically from context.
disambiguate-plan
Thorough collaborative planning with iterative disambiguation - resolves all ambiguity before planning.
pr-review
Review a GitHub pull request: analyzes changed files to select relevant reviewers, loads project and user memory, runs reviewers in parallel, lets the user pick which findings to post, then submits the review on behalf of the user via gh CLI.
dataviz
Define chart types, color encoding, and data display conventions.
build
Implement the next ready task from .forge/tasks.yaml using TDD discipline.
db
Design schema, migrations, indexes, and query patterns with safety guardrails.