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/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/commands/athola/claude-night-market/catchup)<a href="https://agentmods.dev/commands/athola/claude-night-market/catchup"><img src="https://agentmods.dev/badge/commands/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/commands/athola/claude-night-market/catchup"><img src="https://agentmods.dev/badge/commands/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.00025 | $0.00282 |
| Opus 5 | $0.00013 | $0.00141 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
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 6d 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.
What it actually says
Catchup on Changes
Rapidly acquires context on recent changes using imbue's catchup methodology: confirm context, capture delta, extract insights, and record follow-ups.
Invoke Skill(imbue:catchup), which carries the four-step methodology, the
output format and its sections, and the token-conservation rules.
Usage
# Catchup from last known state
/catchup
# Catchup from specific baseline
/catchup HEAD~10
# Catchup from date
/catchup --since "2 days ago"
Examples
/catchup
# Output:
# Catchup Summary
# ===============
# Scope: feature/payments branch
# Baseline: main (merge-base)
# Current: HEAD (15 commits ahead)
#
# Key Changes:
# - Payment processing overhaul (12 files)
# - New Stripe integration (3 files)
# - Test coverage additions (8 files)
#
# Follow-ups:
# - [ ] Review Stripe API key handling
# - [ ] Verify webhook endpoint security
/catchup --since "1 week ago"
# Week-based catchup with date filtering
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.
- 6d ago First seen · 50 lines · 25 tokens per session scan A 82f6eacb9d6f
catchup is a command published in the GitHub repository athola/claude-night-market (337 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 282 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
setup
Verify ClauDex prerequisites — Codex CLI, authentication, and git.
code-review
Perform a comprehensive code review of recent changes.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
red-team
Stress-test a plan, strategy, PRD, or launch with a room of hostile expert personas before you commit.
quick-commit
Quick commit with automatic formatting, linting, and conventional commit message.
git-push
IMPORTANT: This command ONLY runs when explicitly invoked via /git-push. Do NOT auto-push after commits or modifications. Wait for user to explicitly run /push.