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/derjochenmeyer/claude-code-craft-statusline/statusgit clone --depth 1 https://github.com/derjochenmeyer/claude-code-craft-statuslineWhat 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.00012 | $0.00636 |
| Opus 5 | $0.00006 | $0.00318 |
| Sonnet 5 | $0.00002 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade B, and why
status scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
User-config values live in `~/.claude/settings.json` under `pluginConfigs."craft-statusline".options.*`. Defaults from `plugin.json` apply when an option is unset. How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
craft-statusline:status
Report the active craft-statusline configuration, then render a live preview.
Steps
1. Read the active configuration
User-config values live in ~/.claude/settings.json under pluginConfigs."craft-statusline".options.*. Defaults from plugin.json apply when an option is unset.
jq -r '.pluginConfigs["craft-statusline"].options // {}' ~/.claude/settings.json 2>/dev/null
2. Render a tabular summary
For each known option, show whether it is [x] (enabled) or [ ] (disabled) — falling back to the default when unset:
| Field | Default | Notes |
|---|---|---|
show_model |
true | Model + effort badge |
show_branch |
true | Git branch with state-aware palette |
show_context |
true | Context usage with traffic light |
show_context_alert |
true | ⚠ symbol on yellow/red |
show_rate_limits |
true | 5h / 7d windows |
show_cost |
false | API cost (only meaningful on pay-per-token plans) |
show_color |
true | ANSI color globally |
Plus thresholds: context_alert_at (red percent), context_degrade_at_tokens (yellow tokens).
3. Live preview
Run the renderer with a sample payload so the user sees the actual ANSI output. Note that ANSI escapes may not render in this output panel — they will look right in the actual status line at the bottom of Claude Code.
echo '{"model":{"display_name":"Sonnet 4.6"},"context_window":{"used_percentage":42,"current_usage":{"input_tokens":1,"cache_creation_input_tokens":1000,"cache_read_input_tokens":150000}},"rate_limits":{"five_hour":{"used_percentage":15},"seven_day":{"used_percentage":30}},"cost":{"total_cost_usd":0.43}}' \
| bash "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/craft-statusline-marketplace}/scripts/craft-statusline.sh"
The ${CLAUDE_PLUGIN_ROOT:-...} fallback mirrors the pattern in commands/install.md. Statusline lives outside the plugin system, so the variable is not populated in the statusline subprocess (expected behaviour per anthropics/claude-code#52079, closed as "expected existing behavior"). The fallback path resolves to the version-stable marketplace clone.
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.
- 3d ago First seen · 54 lines · 12 tokens per session scan B 3410834b2e9a
status is a command published in the GitHub repository derjochenmeyer/claude-code-craft-statusline (2 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 636 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
ask
Ask a peer session a question and wait for its answer.
setup
Prepare the current project for UIForge — ensure shadcn init, the component registries (shadcn + @motion-primitives), and the motion/lucide-react/cn prerequisites.
init
Initialize project documentation, preferences, or design tokens.
ace:status
Quick project status check with compact output.
kerberos
Kerberos attacks — AS-REP roasting and Kerberoasting.