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/briansmith80/claude-code-status-barWrote 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/briansmith80/claude-code-status-bar/setup)<a href="https://agentmods.dev/commands/briansmith80/claude-code-status-bar/setup"><img src="https://agentmods.dev/badge/commands/briansmith80/claude-code-status-bar/setup/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/briansmith80/claude-code-status-bar/setup"><img src="https://agentmods.dev/badge/commands/briansmith80/claude-code-status-bar/setup.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.00012 | $0.01429 |
| Opus 5.5 | $0.00005 | $0.00572 |
| Sonnet 5.5 | $0.00002 | $0.00286 |
| Haiku 4.5 | $0.00001 | $0.00143 |
Grade A, and why
setup 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-code-status-bar Setup
You are setting up the claude-code-status-bar plugin. Follow these steps exactly.
Step 1: Detect Environment
Run these commands to detect the platform and locate the plugin:
echo "OS: $(uname -s)" && echo "Shell: $SHELL" && echo "Home: $HOME"
Find the plugin installation directory:
plugin_dir=""
for d in "${CLAUDE_CONFIG_DIR:-$HOME/.claude}"/plugins/cache/claude-code-status-bar/claude-code-status-bar/*/; do
[ -d "$d" ] && plugin_dir="$d"
done
echo "Plugin dir: ${plugin_dir:-NOT FOUND}"
Step 2: Install Files
Copy the statusline script and helper to ~/.claude/:
target_dir="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
cp "${plugin_dir}statusline-command.sh" "${target_dir}/statusline-command.sh"
chmod +x "${target_dir}/statusline-command.sh"
# Copy Node.js helpers: live activity line + subagent panel rows
# (optional but recommended)
if [ -f "${plugin_dir}statusline-helper.js" ]; then
cp "${plugin_dir}statusline-helper.js" "${target_dir}/statusline-helper.js"
fi
if [ -f "${plugin_dir}statusline-subagent.js" ]; then
cp "${plugin_dir}statusline-subagent.js" "${target_dir}/statusline-subagent.js"
fi
# Copy version file
if [ -f "${plugin_dir}VERSION" ]; then
cp "${plugin_dir}VERSION" "${target_dir}/.statusline-version"
fi
# Commented config template: always refresh the reference, and create the live
# statusline.conf from it on first install only — never overwrite an existing one.
if [ -f "${plugin_dir}statusline.conf.example" ]; then
cp "${plugin_dir}statusline.conf.example" "${target_dir}/statusline.conf.example"
[ -f "${target_dir}/statusline.conf" ] || cp "${plugin_dir}statusline.conf.example" "${target_dir}/statusline.conf"
fi
echo "Files installed to ${target_dir}"
Step 3: Configure Settings
Read the current settings.json and merge in the statusLine configuration:
target_dir="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
settings_file="${target_dir}/settings.json"
command_value="bash ${target_dir}/statusline-command.sh"
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 · 128 lines · 12 tokens per session scan A 51eb97f43189
setup is a command published in the GitHub repository briansmith80/claude-code-status-bar (18 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 1,429 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
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
safe-build
Build the application for development or production.
create-task-list.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.