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/mischasigtermans/laravel-altitudeWrote 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/mischasigtermans/laravel-altitude/catchup)<a href="https://agentmods.dev/commands/mischasigtermans/laravel-altitude/catchup"><img src="https://agentmods.dev/badge/commands/mischasigtermans/laravel-altitude/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/mischasigtermans/laravel-altitude/catchup"><img src="https://agentmods.dev/badge/commands/mischasigtermans/laravel-altitude/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.00013 | $0.00271 |
| Opus 5 | $0.00006 | $0.00135 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
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 10d 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 - Resume After Break
Get up to speed on current work state.
Usage
/catchup
Workflow
-
Git State
git branch --show-current git status git log --oneline -5 git diff --stat -
App State
- Check
storage/logs/laravel.log(last hour or 10 entries) - Run
php artisan test
- Check
-
Issue Context
- Parse branch for ID:
feature/LIN-123-*,fix/LIN-123-* - If Linear MCP: fetch issue
- If unavailable: show parsed ID
- Parse branch for ID:
-
Summary
## Current State **Branch:** [name] ### Recent Commits - [summaries] ### Uncommitted Changes - [files] ### Issue - [details] ### App Health - [errors] - [test results] ### Next Steps 1. [action] -
Continue - Suggest next action or agent
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.
- 10d ago First seen · 59 lines · 13 tokens per session scan A a0a9347a85c6
catchup is a command published in the GitHub repository mischasigtermans/laravel-altitude (122 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 271 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-08-30.
Other commands, from other repositories
unbloat
Remove dead code, duplicate files, and unused dependencies with user approval at each step. Backs up before deleting.
upgrade-project
Update existing project configurations to current best practices with selective component upgrades.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
promote-discussions
Check GitHub Discussions for highly voted learnings and promote them to Issues.
justify
Audit changes for additive bias, Iron Law compliance, and minimal intervention. Justifies every change against a "simplest safe change" standard.
catchup
Context recovery after session breaks. Summarize recent git changes, extract key decisions, and identify pending work.