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/postmodum37/simple-claude-code-statusline/setupgit clone --depth 1 https://github.com/Postmodum37/simple-claude-code-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.00010 | $0.00251 |
| Opus 5 | $0.00005 | $0.00125 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade B, and why
setup 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. **Read ~/.claude/settings.json** What it actually says
Simple Statusline Setup
Configure the user's statusline setting to use this plugin.
Steps:
-
Create symlink at ~/.claude/statusline.sh
- Find the plugin's script at
${CLAUDE_PLUGIN_ROOT}/bin/statusline.sh - Create symlink:
ln -sf "${CLAUDE_PLUGIN_ROOT}/bin/statusline.sh" ~/.claude/statusline.sh - This allows plugin updates to work automatically
- Find the plugin's script at
-
Read ~/.claude/settings.json
- Create the file with
{}if it doesn't exist
- Create the file with
-
Add/update the statusLine config:
{ "statusLine": { "type": "command", "command": "~/.claude/statusline.sh" } }- Preserve all other existing settings
- The symlink points to the plugin, so updates work automatically
-
Confirm success
- Tell the user the statusline is configured
- Mention that future plugin updates will work automatically
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 · 40 lines · 10 tokens per session scan B b1f4d17eec9d
setup is a command published in the GitHub repository Postmodum37/simple-claude-code-statusline (5 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 251 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
setup
Install the claude-pace statusline bundled with this plugin.
setup
Install & set up newsline — rotating regional news in your status line (keeps your existing status line).
tmux-squad
Open a grid of panes for watching several agents at once — one primary plus N workers.
tmux-project
Open (or reuse) a project workspace session — server / agent / editor.
tmux-status
Show every live tmux session, pane, and exit code, with attach commands.
configure
Reconfigure ccvitals modules and layout.