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 xanoysky/catchup-claude-plugin --skill scangit clone --depth 1 https://github.com/xanoysky/catchup-claude-pluginWrote 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/xanoysky/catchup-claude-plugin/scan)<a href="https://agentmods.dev/skills/xanoysky/catchup-claude-plugin/scan"><img src="https://agentmods.dev/badge/skills/xanoysky/catchup-claude-plugin/scan.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.1 | $0.00064 | $0.00806 |
| Opus 5 | $0.00032 | $0.00403 |
| Sonnet 5 | $0.00013 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
scan 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 7d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catchup
Fetches and summarizes recent changelogs into a single scannable digest.
Arguments
| Argument | Example | Action |
|---|---|---|
| (empty) | /catchup |
Fetch all sources |
| names | /catchup claude,codex |
Fetch only matching sources |
--add |
/catchup --add "Cursor" https://www.cursor.com/changelog |
Add a source |
--remove |
/catchup --remove cursor |
Remove a source |
--list |
/catchup --list |
Show current sources |
--reset |
/catchup --reset |
Restore defaults |
Workflow
1. Handle Management Commands
If $ARGUMENTS starts with --:
- Read config-format.md for the workflow of each command
- Write changes to
~/.catchup/catchup.json - Stop — do not fetch changelogs
2. Load Sources
- Read
~/.catchup/catchup.json - If missing or invalid, read default-sources.json
3. Apply Filters
If $ARGUMENTS contains comma-separated names (no -- prefix):
- Split by comma, trim, lowercase each token
- Keep only sources whose
name(lowercased) contains any token - If no match, list available source names and stop
4. Fetch Changelogs
For each source:
- If the source has a
repofield (e.g."owner/repo"), or theurlmatchesgithub.com/{owner}/{repo}/releases:- Run
gh release list --repo {owner/repo} --limit 3via Bash - Then run
gh release view {tag} --repo {owner/repo}for each tag to get details - If
ghsucceeds → use this data, skip steps 2–3
- Run
- Call WebFetch with the source
urland this prompt (prepend the source'sprompt_hintif present):Extract recent changelog/release entries. Return a structured list: ### [version or date] - Change description Keep it concise — maximum 10 bullet points total across all entries. If no recent entries are found, say "No recent changes found." - If WebFetch fails → try WebSearch with query:
"[source name] changelog latest release [current year]" - If all methods fail → record the error, continue to next source
What ships with it
3 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.
- 7d ago First seen · 73 lines · 64 tokens per session scan A 8e5efdba9e7d
scan is a skill published in the GitHub repository xanoysky/catchup-claude-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 806 once invoked, about $0.0003 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.