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 athola/claude-night-market --skill catchupgit clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/athola/claude-night-market/catchup)<a href="https://agentmods.dev/skills/athola/claude-night-market/catchup"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/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/athola/claude-night-market/catchup"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/catchup.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.00031 | $0.00791 |
| Opus 5.5 | $0.00012 | $0.00316 |
| Sonnet 5.5 | $0.00006 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
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 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catchup Analysis Methodology
Overview
Structured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revisions, or system logs. Answers "what changed and what matters?" efficiently.
When To Use
- Joining ongoing work or returning after absence
- Before planning or reviewing handoffs
- Any "what happened and what's next" context
When NOT To Use
- Doing detailed diff analysis - use diff-analysis instead
- Full code review needed
- use review-core instead
Activation
Keywords: catchup, summary, status, progress, context, handoff Cues: "get me up to speed", "current status", "summarize progress"
Progressive Loading
Load modules based on context:
Git: Load modules/git-catchup-patterns.md for git commands. Consider sanctum:git-workspace-review for initial data gathering.
Documents/Notes: Load modules/document-analysis-patterns.md for meeting notes, sprint tracking, document revisions.
Logs/Events: Load modules/log-analysis-patterns.md for time-series and metric analysis.
Always Available: imbue:proof-of-work, TodoWrite workflow, structured output.
Required TodoWrite Items
catchup:context-confirmed- Boundaries establishedcatchup:delta-captured- Changes enumeratedcatchup:insights-extracted- Themes identifiedcatchup:followups-recorded- Actions captured
4-Step Methodology
Step 1: Confirm Context
Define scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.
Step 2: Capture Delta
Enumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.
Step 3: Extract Insights
Per item: What (change), Why (motivation), Implications (tests/risks/deps). Rollup into themes.
Step 4: Record Follow-ups
Capture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.
Output Format
## Summary
[2-3 sentence theme + risk overview]
## Key Changes
- [Item]: [what/why/implication]
## Follow-ups
- [ ] [Action with owner]
## Blockers/Questions
- [Item requiring resolution]
Verification: Run the command with --help flag to verify availability.
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.
- 1mo ago First seen · 106 lines · 31 tokens per session scan A 410efb92236c
catchup is a skill published in the GitHub repository athola/claude-night-market (343 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 791 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-18.
Other skills, from other repositories
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
github-triage
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
work
Pick up ready leaf yaks and implement them — dispatch subagents in isolated worktrees, then merge back to main.
issue-grooming
Use when the user wants to groom, triage, prioritize, or clean up the GitHub issue backlog of a repo: "groom the issues", "triage the backlog", "which issues are already done", "prioritize the open issues", "close stale issues", "label issues 1-5", "refactor old issues to match the repo", or a periodic backlog review…