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 agentmods add instructions/wasulajr/headsup/claude-mdgit 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/instructions/wasulajr/headsup/claude-md)<a href="https://agentmods.dev/instructions/wasulajr/headsup/claude-md"><img src="https://agentmods.dev/badge/instructions/wasulajr/headsup/claude-md.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 | $0.00658 | $0.00658 |
| Opus 5 | $0.00329 | $0.00329 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
headsup CLAUDE.md 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 4d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
headsup: instructions for Claude sessions working in this repo
Releases are mandatory (issue #19)
Any push to main that changes behavior (features, fixes, skills, hooks, scripts, setup) MUST go through the release script. Never push release-worthy commits bare.
scripts/release.sh <major|minor|patch> -m "what changed" [-m "more" ...]
The script bumps VERSION, prepends a CHANGELOG.md section, commits, tags vX.Y.Z, and pushes main with tags. It refuses to run on a dirty tree or off main, so land your feature commits first, then cut the release.
Semver convention:
- PATCH: bug fixes, doc corrections that affect usage
- MINOR: new features, new skills, new hooks
- MAJOR: breaking conf or layout changes that require re-running
setup.sh
Pure typo/comment-only pushes may skip a release, but say so explicitly in the conversation when skipping.
Bootstrap files
VERSION at the repo root is the installed-version source of truth for scripts; git describe --tags is the fallback for dev checkouts between releases.
Authoring skills (SKILL.md frontmatter)
Every skill's SKILL.md opens with a YAML frontmatter block (name, description). Skill loaders (Claude Code, Codex, and the ~/.agents/skills scanner) parse that YAML and silently skip any skill whose frontmatter fails to parse: there is no error, the skill simply never appears in the menu. Debugging this from the symptom ("my skill is missing") is painful because the file is right there on disk, so prevent it at authoring time.
The most common break is an unquoted colon in the description. In YAML a plain (unquoted) scalar cannot contain ": " (a colon followed by a space): the parser reads it as the start of a nested mapping and throws mapping values are not allowed in this context. This line is invalid, so the skill vanishes:
description: Change colors for Codex sessions: idle, working, and waiting.
Rule: if a frontmatter value contains a colon, or starts with a character YAML treats specially ([ { # & * ! | > % @ or a backtick), wrap the whole value in double quotes. Quoting is always safe, so when in doubt, quote it:
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.
- 4d ago First seen · 48 lines · 658 tokens per session scan A e376afb298cf
headsup CLAUDE.md is an instructions file published in the GitHub repository wasulajr/headsup (1 stars, last pushed 16d ago), licensed MIT. It adds 658 tokens to every session, about $0.0033 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 instructions, from other repositories
claude-code-artifacts-public CLAUDE.md
Instructions for alex-feel/claude-code-artifacts-public, covering claude.md, readme maintenance, category order, a category appears only when it has content and only standalone artifacts are cataloged.
claude_extensions CLAUDE.md
Instructions for kimon1230/claude_extensions, covering global claude.md, persona, hard rules, code quality and planning.
dot-claude-plugins CLAUDE.md
Instructions for and3r817/dot-claude-plugins, covering claude.md, repository overview, core architecture principles, testing commands and run all test suites (master runner).
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.