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-updategit 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-update)<a href="https://agentmods.dev/skills/wasulajr/headsup/headsup-update"><img src="https://agentmods.dev/badge/skills/wasulajr/headsup/headsup-update.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.00023 | $0.00068 |
| Opus 5 | $0.00012 | $0.00034 |
| Sonnet 5 | $0.00005 | $0.00014 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
headsup-update 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 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.
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
Codex Headsup Update
Run:
bash ~/.codex/hooks/headsup-codex-update.sh
Let the script output stand on its own unless it fails.
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 · 15 lines · 23 tokens per session scan A b49fa472949c
headsup-update is a skill published in the GitHub repository wasulajr/headsup (1 stars, last pushed 19d ago), licensed MIT. It adds 23 tokens to every session and 68 once invoked, about $0.0001 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
prompt-sensei
Stage-aware prompt coaching, prompt improvement, lookback analysis, prompting habit feedback, and local reports about prompt quality for AI coding agents such as Claude Code or Codex.
critical-review
Use when you want structured feedback on a plan or document before implementation.
save
Save all session progress to status tracking files. Use when you want to checkpoint work mid-session or before ending.
elderly-ui-audit
A code review for making websites and mobile apps easier for older people to use, based on Chinese government accessibility guidelines.
skill-valet
Use when the session feels bloated or slow, the user mentions "too many skills", "context bloat", "skill list is huge", asks why a skill disappeared or isn't available, or wants to manually park/unpark skill groups mid-session. skill-valet automatically moves unused user-skill directories out of /.claude/skills so the…
code-review
Use when you want a thorough code review of files, changes, or the entire project before shipping.