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 wasulajr/headsup --skill headsup-configgit clone --depth 1 https://github.com/wasulajr/headsupWrote 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/wasulajr/headsup/headsup-config)<a href="https://agentmods.dev/skills/wasulajr/headsup/headsup-config"><img src="https://agentmods.dev/badge/skills/wasulajr/headsup/headsup-config/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/wasulajr/headsup/headsup-config"><img src="https://agentmods.dev/badge/skills/wasulajr/headsup/headsup-config.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.00153 | $0.01314 |
| Opus 5 | $0.00077 | $0.00657 |
| Sonnet 5 | $0.00031 | $0.00263 |
| Haiku 4.5 | $0.00015 | $0.00131 |
Grade A, and why
headsup-config 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/headsup-config: headsup settings hub
One entry point for every headsup setting. The first word of the arguments selects a section; the rest is that section's own arguments, passed straight through to the same backing helper the dedicated skill uses. The focused skills (/headsup-colors, /headsup-label, /headsup-notifications) still exist and auto-trigger on natural phrasing; this is the unified manual entry point, and it is the ONLY skill for the New Claude Tab launch mode (there is no separate /headsup-newtab-args).
Sections
| Section | What it sets | Backing helper |
|---|---|---|
newtabs |
New Claude Tab (Cmd-Opt-C) launch mode | ~/.claude/hooks/headsup-newtab-args.sh |
codextabs |
New Codex Tab launch mode | ~/.claude/hooks/headsup-newtab-args.sh --codex |
colors |
idle / processing / waiting tab colors (global) | the /headsup-colors procedure |
label |
this tab's title + badge (per-session) | ~/.claude/hooks/headsup-set-label.sh |
notify |
the "Claude is waiting" macOS notification | ~/.claude/hooks/headsup-notifications.sh |
Accepted section aliases: newtab/autorun -> newtabs; codex/codextab -> codextabs; color -> colors; title/badge -> label; notifications -> notify.
What to do when invoked
-
Parse the arguments. The first whitespace-delimited token is the
section; everything after it isrest(may be empty). Map aliases to a canonical section above. -
No section, or
show/status/help: show every current setting, then stop. Run these (read-only) and summarize the output:~/.claude/hooks/headsup-newtab-args.sh --show ~/.claude/hooks/headsup-newtab-args.sh --codex --show ~/.claude/hooks/headsup-notifications.sh # prints current notify state grep -E '^(IDLE|PROCESS|WAIT)_COLOR=' ~/.claude/hooks/headsup-status.confAlso note the current per-session label is whatever
/headsup-labellast set (mention it is per-tab). List the sections so the user knows what they can change.
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.
- 8d ago First seen · 68 lines · 153 tokens per session scan A c8c5425c6a77
headsup-config is a skill published in the GitHub repository wasulajr/headsup (1 stars, last pushed 21d ago), licensed MIT. It adds 153 tokens to every session and 1,314 once invoked, about $0.0008 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
mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
phx-mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".
phx-freeze
Apply an advisory edit scope in this session. Use for read-only or directory-scoped work; no enforcement hook is installed.
update-turbo
Update installed Turbo skills from the local repo with a dynamic changelog, conflict resolution for customized skills, and guided user experience. Use when the user asks to "update turbo", "update turbo skills", "reinstall turbo", or "upgrade turbo".