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/weihaog1/claude-code-statusline-alansauce/setupgit clone --depth 1 https://github.com/weihaog1/claude-code-statusline-alansauceWrote 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/weihaog1/claude-code-statusline-alansauce/setup)<a href="https://agentmods.dev/commands/weihaog1/claude-code-statusline-alansauce/setup"><img src="https://agentmods.dev/badge/commands/weihaog1/claude-code-statusline-alansauce/setup.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.00020 | $0.00809 |
| Opus 5 | $0.00010 | $0.00404 |
| Sonnet 5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade C, and why
setup scanned grade C with 3 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Linux (Debian/Ubuntu): `sudo apt install jq` Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Read `~/.claude/settings.json` and update (or add) the `statusLine` key with this value: Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Check that `jq`, `bash`, and `curl` are available: How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Instructions
You are setting up the claude-code-statusline-alansauce statusline plugin. Follow these steps exactly.
Step 1: Find the installed plugin path
Run this command to find where the plugin is installed:
ls -td ~/.claude/plugins/cache/claude-code-statusline-alansauce/claude-code-statusline-alansauce/*/ 2>/dev/null | head -1
Save the output path - you'll need it. If no output is returned, the plugin is not installed. Tell the user to run:
/plugin marketplace add weihaog1/claude-code-statusline-alansauce
/plugin install claude-code-statusline-alansauce
Then retry this setup.
Step 2: Verify dependencies
Check that jq, bash, and curl are available:
command -v jq && command -v bash && command -v curl
If jq is missing, tell the user to install it:
- macOS:
brew install jq - Linux (Debian/Ubuntu):
sudo apt install jq - Linux (Fedora):
sudo dnf install jq - Windows (Git Bash):
choco install jqor download from https://jqlang.github.io/jq/download/
Step 3: Test the plugin
Run a quick test to make sure the script works:
PLUGIN_DIR=$(ls -td ~/.claude/plugins/cache/claude-code-statusline-alansauce/claude-code-statusline-alansauce/*/ 2>/dev/null | head -1)
echo '{"model":{"display_name":"Test"},"context_window":{"current_usage":{"input_tokens":1000},"context_window_size":200000,"used_percentage":5},"cwd":"'$HOME'"}' | bash "${PLUGIN_DIR}statusline.sh"
You should see two lines of colored output. If you see errors, troubleshoot before proceeding.
Step 4: Update settings.json
Read ~/.claude/settings.json and update (or add) the statusLine key with this value:
{
"statusLine": {
"type": "command",
"command": "bash -c 'bash \"$(ls -td ~/.claude/plugins/cache/claude-code-statusline-alansauce/claude-code-statusline-alansauce/*/ 2>/dev/null | head -1)statusline.sh\"'",
"padding": 0
}
}
Use the Edit tool to update ~/.claude/settings.json. Preserve all other existing settings.
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 · 83 lines · 20 tokens per session scan C 1e6dd1206741
setup is a command published in the GitHub repository weihaog1/claude-code-statusline-alansauce (6 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 809 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 3 findings (asks for root, reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.