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 skills/zate/cc-plugins/statuslinenpx skills add Zate/cc-plugins --skill statuslinegit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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.00751 |
| Opus 5 | $0.00006 | $0.00376 |
| Sonnet 5 | $0.00002 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade C, and why
statusline scanned grade C with 2 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 2d 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.
- Ubuntu/Debian: `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 How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devloop Statusline Setup
Configure the devloop statusline to display real-time session information.
What the Statusline Shows
- Model: Current model name (Opus/Sonnet/Haiku)
- Context: Progress bar + percentage of context window used
- Tokens: Total session tokens (formatted as K/M)
- Path: Current working directory (shortened)
- Git Branch: Current branch name
- Plan Progress: Tasks completed (X/Y) from
.devloop/plan.md
Step 1: Read Current Settings
Read the user's Claude Code settings:
Read ~/.claude/settings.json
Step 2: Check Current Status
Analyze the settings to determine the current state:
- No statusLine field: Safe to configure
- Existing devloop statusline: May need path update
- Other statusline: Ask user what to do
Step 3: Get Plugin Path
The devloop statusline script path follows this pattern:
~/.claude/plugins/cache/cc-plugins/devloop/{version}/statusline/devloop-statusline.sh
Find the installed version by checking the plugin cache directory.
Step 4: Handle Based on State
If no statusline configured:
Add the statusLine field to settings.json:
{
"statusLine": {
"type": "command",
"command": "~/.claude/plugins/cache/cc-plugins/devloop/{version}/statusline/devloop-statusline.sh",
"padding": 0
}
}
If existing devloop statusline:
Check if path needs updating (version change). Update if necessary.
If other statusline configured:
AskUserQuestion:
questions:
- question: "You have an existing statusline configured. What would you like to do?"
header: "Statusline"
multiSelect: false
options:
- label: "Replace with devloop"
description: "Use devloop statusline instead"
- label: "Keep existing"
description: "Don't change current statusline"
Step 5: Apply Configuration
Use the Edit tool to update ~/.claude/settings.json with the statusLine configuration.
Step 6: Confirm
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.
- 2d ago First seen · 112 lines · 12 tokens per session scan C 0e976d3aec40
statusline is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 751 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (asks for root, 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…