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 product-on-purpose/agent-skills-toolkit/plugin install agent-skills-toolkitWrote 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/product-on-purpose/agent-skills-toolkit/askit-build-statusline)<a href="https://agentmods.dev/skills/product-on-purpose/agent-skills-toolkit/askit-build-statusline"><img src="https://agentmods.dev/badge/skills/product-on-purpose/agent-skills-toolkit/askit-build-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/product-on-purpose/agent-skills-toolkit/askit-build-statusline"><img src="https://agentmods.dev/badge/skills/product-on-purpose/agent-skills-toolkit/askit-build-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.00041 | $0.00460 |
| Opus 5 | $0.00020 | $0.00230 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
askit-build-statusline 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 11d 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.
What it actually says
askit-build-statusline
Purpose
Author and improve a Claude Code status line, following the builder pattern (../../docs/reference/builder-pattern.md). create scaffolds a status line script (it reads the session JSON Claude Code passes on stdin and prints one status line) and registers it under statusLine in settings; improve tightens an existing one. This is a Claude-only component (F-06 asymmetry): Codex has no shipped status line script - it configures a built-in picker via config.toml tui.status_line - so the script targets Claude only. Recipe in references/statusline-recipe.md.
When to use
When authoring a status line, customizing what it displays, or wiring its settings registration.
create mode
- Decide what the line shows (model, cwd, branch, token/context budget) and keep it to a single fast line.
- Author the script: read the session JSON on stdin, print one line, exit fast (it runs often; no slow calls).
- Register it under
statusLineinsettings.json(or the plugin's settings), pointing at the script with${CLAUDE_PLUGIN_ROOT}.
improve mode
- Read the script and its registration; tighten latency (no network/slow shells), correctness, and the displayed fields.
Scope
Claude-only (Standard sec 2.3): the script and its statusLine registration are a Claude Code feature; Codex's status line is a built-in picker set in config.toml, not a distributable script. A plugin shipping a status line declares it for Claude only; its absence on Codex is not a conformance failure (sec 2.3). Settings/permissions more broadly are askit-build-settings.
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.
- 11d ago First seen · 28 lines · 41 tokens per session scan A ab1925a00cd8
askit-build-statusline is a skill published in the GitHub repository product-on-purpose/agent-skills-toolkit (2 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 460 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
re0-upgrade
Bring your installed paperthin skills up to the full current catalog in one step: retire what's been renamed, add every skill you don't have yet, and refresh the rest, all shown and confirmed before anything changes.
stay-within-limits
Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
agent-estate
Perpetual autonomous work loop for Claude Code — no end condition, no memory regression, no context overfill. Maintains a persistent ledger across all sessions.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.