agentmods.dev

statusline-compact-setup

statusline-compact-setup is a skill for Claude Code from artem-from-ua/claude-plugins. It costs 51 tokens per session (1,047 once invoked), scanned B, original, MIT.

A setup procedure for a compact, one-line Claude Code status display showing repository, branch, model, effort, context, and session cost.

In plain words
What is it for?
Installing or switching to the compact status display in Claude Code settings.
Why use it?
It installs the display and handles conflicts when another status display is already configured.

Skill for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: reads .claude/ paths; names the AskUserQuestion tool; positional $N argument.

Part of the statusline-compact plugin — 1 skill shipped together

not rated 11repo today B scan 51 tokens original MIT

Good fit Installing or switching to the compact status display in Claude Code settings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/artem-from-ua/claude-plugins/statusline-compact-setup
View source ↗ artem-from-ua/claude-plugins
Install

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.

Any agent
npx skills add artem-from-ua/claude-plugins --skill statusline-compact-setup
Clone the repo
git clone --depth 1 https://github.com/artem-from-ua/claude-plugins

Made for: Claude Code.

Or install statusline-compact, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for statusline-compact-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/statusline-compact-setup/github.svg)](https://agentmods.dev/skills/artem-from-ua/claude-plugins/statusline-compact-setup)
Your own site
<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/statusline-compact-setup"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/statusline-compact-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.

agentmods 80×15 button for statusline-compact-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/statusline-compact-setup"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/statusline-compact-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,047 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.01047
Opus 5 $0.00026 $0.00524
Sonnet 5 $0.00010 $0.00209
Haiku 4.5 $0.00005 $0.00105

Measured 8d ago against content hash 9a6fb3e1c1c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

statusline-compact-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 8d 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.

Wire the compact single-line statusline into `~/.claude/settings.json`, resolving any
plugins/statusline-compact/commands/statusline-compact-setup/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Statusline Compact Setup

Wire the compact single-line statusline into ~/.claude/settings.json, resolving any conflict with a statusline that is already configured.

Instructions

  1. Ensure the renderer is installed. If ~/.claude/statusline-compact.sh is missing, copy it from the plugin and make it executable:

    cp "$(dirname "$0")/../../scripts/statusline-compact.sh" ~/.claude/statusline-compact.sh
chmod +x ~/.claude/statusline-compact.sh

    (The SessionStart hook normally does this automatically; this is a fallback.)

  2. Read the current statusline command from ~/.claude/settings.json:

    existing=$(jq -r '.statusLine.command // empty' ~/.claude/settings.json 2>/dev/null)

  3. Conflict detection — branch on $existing:

    • No conflict — $existing is empty, the file is missing, or it already equals ~/.claude/statusline-compact.sh → go straight to step 4 (idempotent).

    • Conflict — $existing points at something else. Identify the likely owner by inspecting the path:

      • basename ends in statusline.sh (i.e. NOT statusline-compact.sh) → most likely the statusline plugin (the full three-line statusline with API rate-limit bars).
      • anything else → a user-custom or third-party statusline.

      Report to the user exactly what is currently configured ($existing) and the detected owner, then ask them to choose (use AskUserQuestion):

      • (a) Keep the existing statusline — abort this setup without changes. If it is the statusline plugin and they want it gone, tell them to disable it via /plugin first.
      • (b) Overwrite — replace .statusLine.command with the compact script.

      Only proceed to step 4 on explicit confirmation of option (b). Never overwrite silently.

  4. Write the statusLine field, preserving all other keys. Seed {} first if the file does not exist:

    [ -f ~/.claude/settings.json ] || echo '{}' > ~/.claude/settings.json
tmp=$(mktemp)
jq '.statusLine = {"type":"command","command":"~/.claude/statusline-compact.sh"}' \
  ~/.claude/settings.json > "$tmp" && mv "$tmp" ~/.claude/settings.json

Read the full file on GitHub · 85 lines

Changes

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.

  1. 8d ago First seen · 85 lines · 51 tokens per session scan B 9a6fb3e1c1c0

Subscribe to this mod's changes

statusline-compact-setup is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,047 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens