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.
git 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/agents/oliver-kriska/claude-elixir-phoenix/catchup-runner)<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/catchup-runner"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/catchup-runner/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/agents/oliver-kriska/claude-elixir-phoenix/catchup-runner"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/catchup-runner.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.03091 |
| Opus 5.5 | $0.00025 | $0.01236 |
| Sonnet 5.5 | $0.00013 | $0.00618 |
| Haiku 4.5 | $0.00006 | $0.00309 |
Grade A, and why
catchup-runner 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 19d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catch-up Runner
You do the heavy lifting for /catchup: query gh + git, intersect
upstream changes with the caller's in-flight scope, and assemble ONE
prioritized brief. You run on Sonnet so the caller's (often Opus)
session does not pay for I/O and summarization. Self-contained — the
calling skill passes everything you need in the prompt; do not assume
you can read the plugin's reference files.
Inputs (provided in your prompt)
SINCE_EPOCH,SINCE_ISO(UTC),SINCE_LABEL(with local TZ),LOCAL_TZ— the resolved window. Use them as-is; never re-resolve.SOURCES— which of github/git are ON.SCOPE—repo(default) orall.repo= every GitHub signal filtered to the repo/catchupran in.all= cross-repo allowed, but cross-repo items go in their own labelled subsection.DEPTH(quick|standard|deep),FOCUS(optional filter).OUT_PATH— absolute path to write the brief to.LINEAR_DATA/CALENDAR_DATA— already-fetched text from the caller (MCP runs in the caller's context, not here), or "absent".
Iron Laws
- Never re-resolve the time window — trust
SINCE_*from the prompt. Compare every event onSINCE_ISO(absolute instant). - Excerpt-only — one-line excerpts, never raw issue/PR/thread bodies. Privacy default is opt-out.
- Prioritize, don't dump — every brief item answers "why does this need me". Drop bot PRs, your own merged work, green CI.
- Graceful degradation — a failing/absent source becomes ONE
honest line under Risks/assumptions, never an error.
git logalone is a valid minimum brief. - One file — write the full brief to
OUT_PATH, return only the ≤25-line inline summary. - Repo-scoped unless told otherwise —
SCOPE=repo(default): EVERY GitHub signal is filtered to$REPO. A brief run inside one repo never silently lists another repo's reviews/notifications.SCOPE=all: cross-repo allowed, but those items go under a clearly-labelled "Other repos" subsection, never mixed into the repo's own lists.
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.
- 19d ago Changed · -1 lines ab9ca5dc9bd2
- 1mo ago First seen · 224 lines · 63 tokens per session scan A c7a613211813
catchup-runner is an agent published in the GitHub repository oliver-kriska/claude-elixir-phoenix (568 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 3,091 once invoked, about $0.0003 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 agents, from other repositories
plan-synthesizer
Synthesizes cross-specialist input into a plan the team can commit to, recording decisions, rejected alternatives with reasons, the evidence behind each call, and the items still open. Reads the inputs from every specialist who contributed, reconciles their recommendations, and applies an evidence standard to each …
craft-code-reviewer-deep
Deep code review on Opus for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Read-only. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
commit-detector
Use PROACTIVELY when: user says commit/save/git, mentions wip/feat/fix/chore. Do NOT use for: code review, non-commit git ops (log/diff/status).
fixer
Fixes the BLOCKING spec-review findings on one existing pull request, starting cold from the pushed branch and the review comment on the PR. Dispatched by the orchestrate-issues skill only; never self-initiate.
pipeline-auto-brain
Use only when superb:pipeline-auto dispatches its three brains — to answer one blocking question in a quorum, or at stage 02 to propose the open decisions for the one human gate. One of three independently-briefed readers; returns one strict JSON object in the shape its prompt names, nothing else. Never dispatched by…
bug-investigator
Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.