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 letitbk/claude-academic-setup --skill catch-upgit clone --depth 1 https://github.com/letitbk/claude-academic-setupWrote 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/letitbk/claude-academic-setup/catch-up)<a href="https://agentmods.dev/skills/letitbk/claude-academic-setup/catch-up"><img src="https://agentmods.dev/badge/skills/letitbk/claude-academic-setup/catch-up.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.00031 | $0.00997 |
| Opus 5 | $0.00015 | $0.00498 |
| Sonnet 5 | $0.00006 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
catch-up 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 8d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catch Up
Overview
Comprehensive project catch-up that summarizes recent activity, accomplishments, and context. Auto-detects time since last activity and presents relevant information.
When to Use
- Returning to a project after any time away
- Starting a new work session
- Recovering mid-session after interruption
- User says "catch up" or similar
Process
Step 1: Detect Last Activity
Check Claude Code project history for last session timestamp:
# Get project hash for current directory
PROJECT_DIR=$(pwd)
PROJECT_HASH=$(echo -n "$PROJECT_DIR" | sed 's/\//-/g' | sed 's/^-//')
PROJECT_PATH="$HOME/.claude/projects/$PROJECT_HASH"
# Find most recent session file
ls -t "$PROJECT_PATH"/*.jsonl 2>/dev/null | head -1
Calculate time elapsed since last activity.
Step 2: Confirm Time Range
Use AskUserQuestion to confirm scenario based on detected time:
| Time Elapsed | Suggested Range | Description |
|---|---|---|
| < 4 hours | Last 4 hours | Mid-session recovery |
| < 24 hours | Last 24 hours | Daily standup |
| < 7 days | Last 7 days | Returning within week |
| < 14 days | Last 30 days | Returning after 1-2 weeks |
| > 14 days | All history | Long absence |
Present with: "You were last here [X time] ago. Show [suggested range]?"
Options:
- Mid-session (4h)
- Daily (24h)
- This week (7d)
- This month (30d)
- Full history
Step 3: Gather Information (All Sources, Skip Unavailable)
3a. Project Context (for "What is this project?")
- Read CLAUDE.md or README if exists
- Analyze directory structure for project type
- Extract project understanding from chat history
3b. Recently Modified Files
# Find files modified in time range, exclude noise
find . -type f -mtime -<DAYS> \
-not -path "./.git/*" \
-not -path "./node_modules/*" \
-not -path "./__pycache__/*" \
-not -name ".DS_Store" \
-not -name "*.pyc" \
2>/dev/null | head -50
3c. Git Commits (if available)
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.
- 8d ago First seen · 144 lines · 31 tokens per session scan A 997010230e8e
catch-up is a skill published in the GitHub repository letitbk/claude-academic-setup (43 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 997 once invoked, about $0.0002 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.