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/awesomejun/cc-statusline/statusline-setupgit clone --depth 1 https://github.com/AwesomeJun/CC-statuslineWrote 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/awesomejun/cc-statusline/statusline-setup)<a href="https://agentmods.dev/commands/awesomejun/cc-statusline/statusline-setup"><img src="https://agentmods.dev/badge/commands/awesomejun/cc-statusline/statusline-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.00012 | $0.01093 |
| Opus 5 | $0.00006 | $0.00547 |
| Sonnet 5 | $0.00002 | $0.00219 |
| Haiku 4.5 | $0.00001 | $0.00109 |
Grade B, and why
statusline-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 4d 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.
- set `statusLine` in `~/.claude/settings.json` (backing up the previous file first). How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install (or switch) the Awesome Statusline for the user.
How to ask the size — MANDATORY
This section is self-contained — do not rely on the repo's CLAUDE.md being
loaded (it is not loaded when this command runs from the installed plugin in
another project). These rules are duplicated verbatim in CLAUDE.md and the
header comments of install.sh / install.ps1; keep all four identical.
-
You MUST resolve a size before installing. Never install without an explicit size chosen by the user. "Auto" / auto-accept mode is NOT an exception — the user is present and can answer; ask anyway. Recommending
large(below) is only a hint shown inside the menu; it must never become a silent default or let you skip the question. Always ask. -
If the user named a size in
$ARGUMENTS(xs/s/m/l/xlor full name), use it and skip the question. -
Otherwise ask with the AskUserQuestion tool, in TWO steps so all five presets fit the tool's 4-option limit. Match the user's language.
Step 1 — question text:
- EN:
Which size would you like to install? (size examples on GitHub: https://github.com/AwesomeJun/CC-statusline) - KO:
어떤 크기로 설치할까요? (크기 예시는 GitHub에서 확인: https://github.com/AwesomeJun/CC-statusline)
Step 1 — four options, in EXACTLY this order — do NOT reorder. The recommended option is always
large(option 1); never substitutemediumor anything else as the recommendation:large(l) (추천 / Recommended) — most info, good for most users / 추천 기본값xlarge(xl) — largest, full detail / 가장 크게, 전체 상세medium(m) — balanced layout / 균형 잡힌 레이아웃small/xsmall— the two smallest; pick this to choose between them / 작은 두 가지 (고르면 한 번 더 선택)
Step 2 — ONLY if the user picked option 4, ask again:
- EN:
Which of the two smaller sizes?· KO:작은 쪽 중 무엇으로 설치할까요?
small(s) — space-saving, key info / 공간 절약, 주요 정보xsmall(xs) — smallest, essentials only / 가장 작게, 핵심만
If the user gives nothing / "recommended" / "default", use
large. - EN:
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.
- 4d ago First seen · 80 lines · 12 tokens per session scan B 55259f9b17b9
statusline-setup is a command published in the GitHub repository AwesomeJun/CC-statusline (171 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,093 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
analyzer
Deep code and data analysis with batch processing capabilities.
parallel-execution
Execute independent subtasks in parallel for maximum efficiency.
coder
Autonomous code generation with batch file operations.
cache-manage
Command "cache-manage" from ruvnet/RuView, covering cache-manage, usage, options, examples and view cache stats.
topology-optimize
Optimize swarm topology for current workload.
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.