Borrowing it
Nothing to install: this file belongs to DeL-TaiseiOzaki/claude-code-orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DeL-TaiseiOzaki/claude-code-orchestra/main/.claude/skills/catchup/SKILL.mdgit clone --depth 1 https://github.com/DeL-TaiseiOzaki/claude-code-orchestraWrote 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/del-taiseiozaki/claude-code-orchestra/catchup)<a href="https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/catchup"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/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/del-taiseiozaki/claude-code-orchestra/catchup"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/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.00076 | $0.01829 |
| Opus 5.5 | $0.00030 | $0.00732 |
| Sonnet 5.5 | $0.00015 | $0.00366 |
| Haiku 4.5 | $0.00008 | $0.00183 |
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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catchup
Onboarding skill that produces a GUIDE.md at the repository root so a new or returning contributor can understand the project's history, current state, and how to resume work.
When to Use
- A contributor joins the repository for the first time
- A contributor returns after a long absence
- You want a single human-readable snapshot of "what has been happening here"
When NOT to Use
- You need a single focused answer (use
/featureplanning phases or direct research instead) - You want to capture the current session for later (use
/checkpointing) - You want running design history (use
/design-trackeror readDESIGN.mddirectly)
Full skill routing: AGENTS.md section "Routing Policy".
Workflow
Phase 1: COLLECT (collect_repo_state.py)
Run the collector script -> single JSON of every dataset the template needs
|
Phase 2: SYNTHESIZE (Claude Lead)
Turn that JSON into per-section prose — the judgment step
|
Phase 3: ASSEMBLE (write_guide.py)
Stamp, order, validate, and write GUIDE.md under the Writer Safety Contract
Phase 1: COLLECT (via collect_repo_state.py)
python3 .claude/skills/catchup/collect_repo_state.py
Optional flags: --since "30 days ago" (recent-work window, passed to git),
--max-commits 100, --claude-home DIR (Agent Teams data root),
--project-root DIR.
Exit codes: 0 ok · 1 bad arguments · 2 not a git repository, or a
SKILL.md/agent frontmatter that yields neither a name nor a description ·
3 a git subcommand failed inside a real repository. The payload always carries
top-level ok and errors; check those rather than assuming exit 0.
Degradation is named, never silent: an absent file is {"present": false}, an
unreadable one carries an error, and a failed git subcommand is null plus an
entry in git.errors — distinct from [], which means genuinely empty.
Top-level JSON keys:
git—log,branches,status,stash,diffstat,recent_stat,current_branch,errors.identity—README.md,AGENTS.md,pyproject.tomlpresence + first line, plusidentity.statewithmain_agent,current_project,current_feature,current_bug_fixread from.claude/STATE.md.rules—{present, items[{file, first_line}]}.skills—{present, items[{name, short_description, file}], frontmatter_errors}.agents—{present, items[{name, specialization, model, file}], frontmatter_errors}.docs—design{present, placeholder, key_decisions[]},research,libraries.env—manifests,scripts(frompyproject.toml),commands(each with thesourcefile it was quoted from),errors.checkpoints— newest 5 (file +first_line: the frontmattersummary, else itsslug, else the first non-empty body line — never the---fence).agent_teams—sessions[{name, members, tasks_total, tasks_completed}]and in-repowork_logs.cli_tools— recent consultations for every tool, each tagged withtool, plusskipped_lines.
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 Changed b425585589a2
- 1mo ago Changed d186e29a9d26
- 2mo ago Changed · +1 lines · +1 tokens per session 04a6ec5ea681
- 2mo ago First seen · 176 lines · 75 tokens per session scan A 7e963e6041d8
catchup is a skill published in the GitHub repository DeL-TaiseiOzaki/claude-code-orchestra (198 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 1,829 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.
catchup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| catchupDeL-TaiseiOzaki/claude-code-orchestra | Skill | 198 | 5d ago | MIT | A | 76 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |