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 MadAppGang/magus --skill statusline-customizationgit clone --depth 1 https://github.com/MadAppGang/magusWrote 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/madappgang/magus/statusline-customization)<a href="https://agentmods.dev/skills/madappgang/magus/statusline-customization"><img src="https://agentmods.dev/badge/skills/madappgang/magus/statusline-customization/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/madappgang/magus/statusline-customization"><img src="https://agentmods.dev/badge/skills/madappgang/magus/statusline-customization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 381 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 358 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 380 Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.Fix: Remove unnecessary filesystem scanning. If file access is needed, use explicit, scoped paths. Avoid reading ~/.ssh, ~/.aws, or credential directories.
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.00025 | $0.05419 |
| Opus 5.5 | $0.00010 | $0.02168 |
| Sonnet 5.5 | $0.00005 | $0.01084 |
| Haiku 4.5 | $0.00003 | $0.00542 |
Grade A, and why
statusline-customization 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 22d 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 — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Statusline Customization Reference
Config File
Location: ~/.claude/statusline-config.json
Schema
{
"sections": {
"model": true, // Model name (Opus/Sonnet/Haiku)
"branch": true, // Git branch name
"worktree": true, // Worktree indicator (wt:name)
"cost": true, // Session cost ($X.XX)
"duration": true, // Session duration (Xm Xs)
"context_bar": true, // Context window usage bar
"plan_limits": true, // Plan limit bars with reset countdowns (master switch)
"claudish_plan": true // Provider plan bars when the session is routed via claudish
},
"icons": {
"nerd_font": false // Opt in to Nerd Font glyphs (RAM → ). Default OFF
},
"context_bar_width": 12, // Width of context bar in chars (8-20)
"plan_bar_width": 10, // Width of plan limit bar in chars (6-16)
"theme": "default", // Color theme name
"appearance": "auto", // "auto" | "light" | "dark" — see Appearance below
"wrap": "auto", // "auto" wraps to the terminal width, "off" forces one line
"max_lines": 0, // Cap on wrapped rows; 0 means no cap
"layout": "auto" // "auto" | "aligned" | "compact" — see Wrapping below
}
All fields are optional. Missing fields use defaults shown above. sections and
icons are independent groups — setting one never affects the other.
theme and appearance are orthogonal: theme picks the palette's character
(default / minimal / neon / monochrome), appearance picks whether that palette is
drawn for a light or a dark terminal.
Appearance
The statusline resolves light vs dark at render time, because the same colours cannot work on both. It follows the same six-step order as magus and tmux-setup, first hit wins:
appearancein this config, when set tolightordark(the script's own flag)$STATUSLINE_APPEARANCE— per-pane override without touching the config (its own variable)$TERM_THEME- OSC 11 probe — no step: the statusline child has no tty (stdin, stdout and stderr are pipes), so there is nowhere to send a background-colour query
COLORFGBG— inside tmux, the session-scope copy read viatmux show-environment; outside tmux, the$COLORFGBGenvironment variabledark
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.
- 22d ago Changed · +3 lines 4ede5d84c8a7
- 28d ago Changed 8a38d58084f0
- 1mo ago Changed 4eb6ba8fbb1b
- 1mo ago Changed · +24 lines d00e27c20a57
- 1mo ago First seen · 401 lines · 25 tokens per session scan A 6e975e7d8d77
statusline-customization is a skill published in the GitHub repository MadAppGang/magus (13 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 5,419 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-04.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…