Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add hg-pyun/claude-code-marketplace/plugin install dev-toolsWrote 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/skills/hg-pyun/claude-code-marketplace/install-statusline)<a href="https://agentmods.dev/skills/hg-pyun/claude-code-marketplace/install-statusline"><img src="https://agentmods.dev/badge/skills/hg-pyun/claude-code-marketplace/install-statusline/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/skills/hg-pyun/claude-code-marketplace/install-statusline"><img src="https://agentmods.dev/badge/skills/hg-pyun/claude-code-marketplace/install-statusline.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.00220 | $0.01854 |
| Opus 5 | $0.00110 | $0.00927 |
| Sonnet 5 | $0.00044 | $0.00371 |
| Haiku 4.5 | $0.00022 | $0.00185 |
Grade B, and why
install-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 10d 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.
- Default scope is **user** (`~/.claude/settings.json`). Use `--scope=project` only when the user wants the status line wired at the project level. How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- User wants to install / set up / replicate the project's standard status line ("상태줄 깔아줘", "install the status line")
- User invokes
/install-statusline(optionally--scope=projector--dry-run) - A fresh machine or teammate needs the same ccstatusline configuration without manual editing
- The
statusLineblock and/or ccstatusline widget layout is missing or should be reset to the canonical preset </Use_When>
<Do_Not_Use_When>
- User wants to design a brand-new, fully custom status line from scratch → use the built-in
statusline-setupagent instead - User only wants to tweak a single widget or color → edit
~/.config/ccstatusline/settings.jsondirectly or runccstatuslineinteractively - User is asking conceptually what the status line displays — just explain
- User explicitly does not use ccstatusline and wants a different status-line tool </Do_Not_Use_When>
<Why_This_Exists>
A working status line is split across two files — the statusLine block in Claude Code's settings.json (the wiring) and the ccstatusline widget layout in ~/.config/ccstatusline/settings.json (what's actually shown) — plus a globally installed binary. Setting this up by hand is error-prone: editing settings.json risks clobbering unrelated keys, and the widget layout is tedious to recreate. This skill captures the maintainer's current, validated configuration as shipped assets and installs all three pieces atomically with backups, so replication is one command instead of a manual checklist.
</Why_This_Exists>
<Execution_Policy>
- Run the shipped
install.sh— do not hand-edit settings.json with ad-hoc shell. - Always back up any existing target file before overwriting (the script does this; never bypass it).
- The
settings.jsonmerge MUST preserve every existing key — onlystatusLineis added/replaced. - Default scope is user (
~/.claude/settings.json). Use--scope=projectonly when the user wants the status line wired at the project level. - When unsure whether the user wants user-level or project-level install, AskUserQuestion before running.
- Offer
--dry-runfirst if the user is cautious or has an existing custom status line. </Execution_Policy>
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 120 lines · 220 tokens per session scan B 4e0a3d76f90e
install-statusline is a skill published in the GitHub repository hg-pyun/claude-code-marketplace (2 stars, last pushed 2mo ago), licensed MIT. It adds 220 tokens to every session and 1,854 once invoked, about $0.0011 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…