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 skills add charlesjones-dev/claude-code-plugins-dev --skill statusline-editgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/statusline-edit)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/statusline-edit"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/statusline-edit/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/charlesjones-dev/claude-code-plugins-dev/statusline-edit"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/statusline-edit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.01848 |
| Opus 5.5 | $0.00007 | $0.00739 |
| Sonnet 5.5 | $0.00004 | $0.00370 |
| Haiku 4.5 | $0.00002 | $0.00185 |
Grade A, and why
statusline-edit 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 9d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Line Edit
Edit your existing Claude Code status line configuration.
Instructions
CRITICAL: This command MUST NOT accept any arguments. If the user provided any text after this command, COMPLETELY IGNORE it.
Phase 1: Detect Existing Configuration
- Detect the operating system using Bash:
uname -s- "Darwin" = macOS, "Linux" = Linux, otherwise assume Windows
- Check if the status line script exists:
- Mac/Linux:
~/.claude/statusline.sh - Windows:
C:/Users/USERNAME/.claude/statusline.ps1
- Mac/Linux:
- If the script does NOT exist, display:
Then STOP - do not continue.No status line script found at ~/.claude/statusline.sh Run /statusline-wizard to set up your status line first.
Phase 2: Read Current Configuration
Read the existing script file and parse the current SHOW_* variable values:
For Bash scripts, look for lines like:
SHOW_MODEL=true
SHOW_EFFORT=true
SHOW_SANDBOX=false
SHOW_TOKEN_COUNT=true
SHOW_PROGRESS_BAR=true
SHOW_DIRECTORY=true
SHOW_GIT_BRANCH=true
SHOW_COST=false
SHOW_DURATION=true
SHOW_TIME=true
SHOW_VERSION=true
SHOW_RATE_LIMITS=true
SHOW_SPEND_BUDGET=false
SPEND_LIMIT_USD=0
SPEND_RESET_DAY=1
SPEND_RESET_TIME=00:00
For PowerShell scripts, look for lines like:
$SHOW_MODEL = $true
$SHOW_EFFORT = $true
$SHOW_TOKEN_COUNT = $true
$SHOW_PROGRESS_BAR = $true
$SHOW_DIRECTORY = $true
$SHOW_GIT_BRANCH = $true
$SHOW_COST = $false
$SHOW_DURATION = $true
$SHOW_TIME = $true
$SHOW_VERSION = $true
$SHOW_RATE_LIMITS = $true
$SHOW_SPEND_BUDGET = $false
$SPEND_LIMIT_USD = 0
$SPEND_RESET_DAY = 1
$SPEND_RESET_TIME = '00:00'
Store the current values to use as defaults in the wizard.
Note: Scripts generated by older plugin versions may lack SHOW_EFFORT (pre-1.3.0), SHOW_SPEND_BUDGET / SPEND_LIMIT_USD / SPEND_RESET_DAY / SPEND_RESET_TIME (pre-1.4.0), or SHOW_SANDBOX (pre-1.5.0). If a variable is not present in the script, OMIT the matching option from the wizard (toggling it would have no effect) and, after the update completes, mention that re-running /statusline-wizard will regenerate the script with support for the missing segment(s). The exception is SHOW_SANDBOX in a PowerShell script: it's never there, because the sandbox doesn't run on native Windows, so omit the option without suggesting a re-run.
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.
- 9d ago Changed · +4 lines 89c059494d2f
- 1mo ago Changed · +27 lines 405bbaa4de56
- 1mo ago First seen · 136 lines · 18 tokens per session scan A fc03a4a1345c
statusline-edit is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 1,848 once invoked, about $0.0001 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-09-06.
Other skills, from other repositories
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…