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 oliver-kriska/claude-elixir-phoenix --skill catchupgit clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenixWrote 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/oliver-kriska/claude-elixir-phoenix/catchup)<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/catchup"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/catchup/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/oliver-kriska/claude-elixir-phoenix/catchup"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/catchup.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.00048 | $0.01629 |
| Opus 5.5 | $0.00019 | $0.00652 |
| Sonnet 5.5 | $0.00010 | $0.00326 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
catchup 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 21d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catchup — Async-Team Return Briefing
You've been away. This skill is a thin orchestrator: it resolves
the window + sources here, then delegates the I/O fan-out, impact
analysis, and brief assembly to the catchup-runner agent (Sonnet) so
your (often Opus) session does not pay for summarization. You only
print what the agent returns.
Usage
/catchup # since you were last active
/catchup --since "friday"
/catchup --since "2h" --focus reviews-requested
/catchup --since last-commit --depth deep
/catchup --scope all # include cross-repo pings/reviews
Default is repo-scoped: every GitHub signal (reviews requested,
notifications, mentions) is filtered to the repo you ran it in. Pass
--scope all to also include cross-repo activity, which is then listed
in its own separate section — never mixed into this repo's lists.
Iron Laws
- Delegate the heavy work — spawn
catchup-runner(sonnet) for fan-out + assembly. Do NOT run thegh/gitfan-out in this session; that defeats the cost/speed purpose. - Resolve the window here, once — the agent must never re-resolve
it. Pass absolute
SINCE_*values. - MCP runs here, not in the agent — Linear/Calendar MCP tools are unreliable in subagents. If present, fetch in this context and pass the text to the agent; else mark absent.
- Validate
--sincebefore any shell — match the grammar; on no match fall back to 24h and note the assumption. - Stop after the brief — print the agent's summary, never auto-transition to another command.
- Repo-scoped by default — pass
SCOPE=repounless the user passed--scope all. A brief run inside one repo must not leak another repo's reviews/notifications. Cross-repo is opt-in only.
Workflow
1. Parse arguments
From $ARGUMENTS: --since, --scope, --sources, --depth,
--focus. Defaults: --since last-active, --scope repo, all
detected sources, --depth standard, no focus. --scope accepts
repo (default — every GitHub signal filtered to the current repo) or
all (cross-repo allowed, listed in its own section).
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 21d ago Changed · -1 lines 76be0877ad3b
- 22d ago Changed fb6fa804bf6c
- 1mo ago First seen · 139 lines · 48 tokens per session scan A 7c6e3c70fe04
catchup is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (569 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 1,629 once invoked, about $0.0002 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-30.
Other skills, from other repositories
craft-plugin-release
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
github-activity
Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.
implement-issue
Turn one labelled GitHub issue into one reviewed pull request, or stop with a stated reason. Use for every factory run; the message is a link to the issue.
git-commit
Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have.".
standup
Write a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week.