Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/oxi-717/ai-native-toolkit/statusline-setup)<a href="https://agentmods.dev/skills/oxi-717/ai-native-toolkit/statusline-setup"><img src="https://agentmods.dev/badge/skills/oxi-717/ai-native-toolkit/statusline-setup.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.00056 | $0.01152 |
| Opus 5 | $0.00028 | $0.00576 |
| Sonnet 5 | $0.00011 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade B, and why
statusline-setup scanned grade B 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 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.
Add to `~/.claude/settings.json`: Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl` — API calls How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Statusline Setup
What It Shows
project (branch) • Fable 5 • 2h15m 73% W100% F8%->Sonnet • $0.00 • CTX▼88%
| Segment | Source | Description |
|---|---|---|
project (branch) |
JSON stdin | Working dir + git branch |
Fable 5 |
JSON stdin | Current model |
2h15m 73% |
OAuth API | Time until 5h reset + remaining capacity |
W100% |
OAuth API | 7-day weekly capacity remaining |
F8%->Sonnet |
OAuth API | Fable 5 weekly scoped capacity is at/below fallback threshold |
$0.00 |
JSON stdin | Session cost ($0.00 on Max) |
CTX▼88% |
JSON stdin | Context window remaining |
Color Coding
| Metric | Green | Yellow | Red |
|---|---|---|---|
| Limits (remaining) | >50% | 20-50% | <20% |
| Context (remaining) | >30% | 10-30% | <10% |
Fable 5 Fallback Policy
Fable 5 is the preferred expensive model only while the model-scoped weekly capacity has enough headroom. For non-interactive research/analysis sessions:
- If Fable 5 remaining capacity is above 10%, keep using Fable 5 when quality justifies it.
- If Fable 5 remaining capacity is 1-10%, switch research/analysis to Sonnet before asking an interactive question.
- If Fable 5 remaining capacity is 0%, treat Fable as exhausted and use Sonnet for research/analysis without prompting.
The SessionStart hook prints the policy when Fable is at/below the threshold. The
statusline marks the scoped limit as F8%->Sonnet or F0%->Sonnet while the policy
is active. The threshold and fallback model can be overridden with
STATUSLINE_FABLE_FALLBACK_THRESHOLD and STATUSLINE_FABLE_FALLBACK_MODEL.
Deferred scope: this plugin does not cache research results. Research-result caching belongs to the specific research/analyzer workflow that can identify semantically equivalent requests and valid reuse boundaries.
Installation
1. Copy script
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-/path/to/installed/statusline}"
cp "$PLUGIN_ROOT/scripts/statusline.sh" ~/.claude/statusline.sh
chmod +x ~/.claude/statusline.sh
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 · 128 lines · 56 tokens per session scan B 958c9d75c586
statusline-setup is a skill published in the GitHub repository OXI-717/ai-native-toolkit (7 stars, last pushed 13d ago), licensed MIT. It adds 56 tokens to every session and 1,152 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by main printing-press SKILL.md (Phase 4.85) and printing-press-polish…
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
semgrep-rule-creator
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.