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 petekp/claude-code-setup --skill catch-upgit clone --depth 1 https://github.com/petekp/claude-code-setupWrote 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/petekp/claude-code-setup/catch-up)<a href="https://agentmods.dev/skills/petekp/claude-code-setup/catch-up"><img src="https://agentmods.dev/badge/skills/petekp/claude-code-setup/catch-up/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/petekp/claude-code-setup/catch-up"><img src="https://agentmods.dev/badge/skills/petekp/claude-code-setup/catch-up.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.00100 | $0.01846 |
| Opus 5.5 | $0.00040 | $0.00738 |
| Sonnet 5.5 | $0.00020 | $0.00369 |
| Haiku 4.5 | $0.00010 | $0.00185 |
Grade A, and why
catch-up 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catch Up
The person reading this has been away. While they were gone, agents (you and others) moved the project forward. They are juggling several projects like this one and do not read the code closely. Your job is to get them back in the driver's seat in under a minute: what changed, why it changed, and where their input would actually steer things.
That framing decides everything below. They cannot act on a diff or a commit list, so do not give them one. They can act on plain ideas and clear choices, so give them those.
What good looks like
- Plain English, zero jargon. Every technical term either gets translated or explained the first time it appears. If a reader who has never seen the code would stumble on a word, rewrite it. See Translating jargon.
- Altitude, not inventory. Group changes by what they mean, not by file. One idea per bullet. The headline is the thing, not the line count.
- The why is the payload. The diff says what changed; only the conversation says why. The reader steers on the why, so make sure it survives.
- Surfaces the forks. The single most useful thing you can give a steerer is the list of decisions that are still open, or were made by default and could be reversed. That is where their attention belongs.
- Honest. If something is half-done, untested, or went sideways, say so. A catch-up that hides loose ends makes steering worse, not better.
How to do it
1. Find the starting line
State the window you are summarizing, in one short phrase, so the reader knows the frame. Infer it from the conversation, in this order:
- A previous catch-up. Scan the transcript for the last time you ran this skill (your own output, led by a window line like the ones below). If you find one, summarize only what happened after it. This is the common case when they check in repeatedly.
- A clear milestone. A merge, a shipped PR, a finished plan, or an explicit "let's start on X" is a natural starting line. Summarize since then and name it: "Since the auth refactor merged".
- The session start. If neither of the above is clear, summarize the whole session and say so: "This session so far".
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 · -6 lines · -66 tokens per session f79351a09c83
- 1mo ago First seen · 169 lines · 166 tokens per session scan A aed3c158ebfc
catch-up is a skill published in the GitHub repository petekp/claude-code-setup (48 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 1,846 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
kanban-video-orchestrator
Plan and run multi-agent video production pipelines.
sdlc-review
Review Kanban handoffs and route verified outcomes.
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for publishartifact, outputiframe, or slackattachhtml.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.