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 paleo/alignfirst --skill alcatchupgit clone --depth 1 https://github.com/paleo/alignfirstWrote 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/paleo/alignfirst/alcatchup)<a href="https://agentmods.dev/skills/paleo/alignfirst/alcatchup"><img src="https://agentmods.dev/badge/skills/paleo/alignfirst/alcatchup/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/paleo/alignfirst/alcatchup"><img src="https://agentmods.dev/badge/skills/paleo/alignfirst/alcatchup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00169 |
| Opus 5.5 | $0.00011 | $0.00068 |
| Sonnet 5.5 | $0.00005 | $0.00034 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
alcatchup 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 1mo 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
Run npx -y alignfirst ticket <ticket-id> --catchup to load the ticket history. If the ticket ID is unknown, run npx -y alignfirst ticket --catchup instead; the CLI deduces it from the branch. When it cannot, ask the user.
Then follow the user's instructions. Without instructions, return a short synthesis: what was requested, decided, done, and left open.
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.
- 1mo ago Changed · +5 lines 0f35d3f41e52
- 1mo ago First seen · 10 lines · 27 tokens per session scan A e67107a0216a
alcatchup is a skill published in the GitHub repository paleo/alignfirst (85 stars, last pushed today), licensed CC0-1.0. It adds 27 tokens to every session and 169 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-03.
Other skills, from other repositories
collaboration
Use for /collaboration, collaboration repair, friction signals, soft-skills coaching, or structured human-Claude interaction techniques such as compromise, rubber ducking, energy checks, pairing, retros, working agreements, and perspective swaps.
therapist
Run a structured human-Claude collaboration retrospective. Use for /therapist, therapy sessions, interaction reviews, workflow check-ins, frustration recovery, or improving how the user and Claude work together.
tmux
Use when a CLI task needs an interactive terminal or control of a tmux session.
refit
Cross-session environment retrospective driven by OMC's own instrumentation — trace timelines, friction reports, logs, and plan notepads. Every finding lands on the surface that owns the fix (deterministic check, steering volume, tooling, or information access); nothing is written without user approval.
minimal-code-discipline
YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away.
meeting-note-summarizer
Turn meeting notes or transcripts into factual summaries, decisions, questions, and action items. Use when a user wants a concise recap or needs explicit owners and deadlines extracted without filling in missing details.