Claude Code Skills Marketplace is a collection and marketplace of skills, plugins, agents, and instructions that extend Claude Code with specialized development workflows. It is for developers who want to install existing workflows or create, validate, and package their own Claude Code skills.
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/daymade/claude-code-skills/statusline-generatornpx skills add daymade/claude-code-skills --skill statusline-generatorgit clone --depth 1 https://github.com/daymade/claude-code-skillsWrote 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/daymade/claude-code-skills/statusline-generator)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/statusline-generator"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/statusline-generator.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.1 | $0.00184 | $0.02318 |
| Opus 5 | $0.00092 | $0.01159 |
| Sonnet 5 | $0.00037 | $0.00464 |
| Haiku 4.5 | $0.00018 | $0.00232 |
Grade B, and why
statusline-generator 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 6d 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.
2. `~/.claude/settings.json` has a valid `statusLine` block pointing at the script. How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Statusline Generator
A single-source-of-truth statusline for Claude Code. One script, two layouts, end-to-end self-verification.
Quick health check (start here when something is wrong)
Run this first whenever the statusline misbehaves. It catches the silent failures that account for most "configured but not working" reports:
bash scripts/health_check.sh
It validates four layers:
~/.claude/statusline.shexists and is executable. Missingchmod +xis the single most common silent-failure cause — Claude Code runs the script,execfails, statusline goes blank.~/.claude/settings.jsonhas a validstatusLineblock pointing at the script.- Mock stdin tests covering complete data, zero tokens, missing fields,
$HOMEpath shortening, and zero-fork git-branch rendering (via a synthetic.git/HEAD— no git binary required). - Real stdin replay from
/tmp/.claude-statusline-last-stdin.jsonif you previously ran withCLAUDE_STATUSLINE_DEBUG=1.
Each failure prints a one-line fix command — you don't have to read documentation to recover.
Quick install
bash scripts/install_statusline.sh
This script:
- Backs up any existing
~/.claude/statusline.shandsettings.json. - Copies
generate_statusline.shto~/.claude/statusline.shandchmod +xs it. - Updates
settings.jsonstatusLineblock viajq(preserves other settings). - Mandatorily runs
health_check.shand shows the result — installation is not "complete" until verification passes.
Restart Claude Code (or send any new message) to see the statusline update.
What you get
Default — minimal one-line layout
~/code/myproject [main] Opus 4.7 (1M context) ctx: 108K / 1M
Just the essentials: short path, git branch, model name, absolute token counts.
No colors, no cost, no percentage. The branch is read zero-fork — the script
reads .git/HEAD as a plain file (with worktree/submodule gitdir: indirection
and detached-HEAD short-sha handling) instead of spawning git, so it costs
nothing and works even on hosts without a git binary.
What ships with it
9 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.
- .security-scan-passed 181 B
- references/ccusage_integration.md 4.1 KB
- references/color_codes.md 2.3 KB
- references/context-window-schema.md 3.8 KB
- references/customization.md 3.8 KB
- references/troubleshooting-decision-tree.md 7.5 KB
- scripts/generate_statusline.sh 8.7 KB runs code
- scripts/health_check.sh 6.0 KB runs code
- scripts/install_statusline.sh 3.4 KB runs code
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.
- 6d ago First seen · 211 lines · 184 tokens per session scan B dff9418e56b5
statusline-generator is a skill published in the GitHub repository daymade/claude-code-skills (1,377 stars, last pushed yesterday), licensed MIT. It adds 184 tokens to every session and 2,318 once invoked, about $0.0009 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 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…
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…
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…