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/arpitnath/claude-capsule-kit/statuslinegit clone --depth 1 https://github.com/arpitnath/claude-capsule-kitWrote 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/arpitnath/claude-capsule-kit/statusline)<a href="https://agentmods.dev/commands/arpitnath/claude-capsule-kit/statusline"><img src="https://agentmods.dev/badge/commands/arpitnath/claude-capsule-kit/statusline.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.00426 |
| Opus 5 | $0.00005 | $0.00213 |
| Sonnet 5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade B, and why
statusline 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 5d 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.
cat ~/.claude/statusline-config.json 2>/dev/null || echo '{"model":true,"duration":true,"context":true,"worktree":true,"crew":true,"capsule_pill":true}' What it actually says
Statusline Configuration
Configure which sections are visible in your Claude Code statusline.
Step 1: Read current config
cat ~/.claude/statusline-config.json 2>/dev/null || echo '{"model":true,"duration":true,"context":true,"worktree":true,"crew":true,"capsule_pill":true}'
Step 2: Show current state and ask what to change
Show the user which sections are currently enabled/disabled, then use AskUserQuestion with multiSelect to let them pick which sections to show. Unselected sections will be hidden.
Sections available:
- Model — Current model name (e.g., Opus, Sonnet)
- Duration — Session duration (e.g., 2h 15m)
- Context — Context window progress bar with percentage
- Worktree — Git worktree indicator pill (only when in a worktree)
- Crew — Crew mode indicator (@crew=name, only when in a crew worktree)
- Capsule Kit — CCK active pill badge
Use AskUserQuestion with multiSelect=true. Pre-select the currently enabled sections by listing them first with "(Enabled)" suffix. The question should be: "Which sections should be visible in the statusline?"
Step 3: Write config
Based on the user's selection, write the config file:
cat > ~/.claude/statusline-config.json << 'CONF'
{
"model": true/false,
"duration": true/false,
"context": true/false,
"worktree": true/false,
"crew": true/false,
"capsule_pill": true/false
}
CONF
Step 4: Confirm
Show the user what changed. List enabled and disabled sections clearly.
Tell the user: "Restart Claude Code to see the changes in your statusline."
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.
- 5d ago First seen · 52 lines · 10 tokens per session scan B 23a451c8273b
statusline is a command published in the GitHub repository arpitnath/claude-capsule-kit (90 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 426 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-30.
Other commands, from other repositories
CONTEXT
Slash commands for SPEC-First development workflow.
catchup
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/catchup/SKILL.md.
statusbar
Show current status-bar config and list available styles + themes.
help
Explain Ralph Wiggum technique and available commands.
memory-list
DEPRECATED: Use Serena listmemories instead. Lists recent memories from Forgetful with optional project filtering.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.