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 agentmods add commands/akshayrao14/git-practices/session-catchupgit clone --depth 1 https://github.com/akshayrao14/git-practicesWrote 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/akshayrao14/git-practices/session-catchup)<a href="https://agentmods.dev/commands/akshayrao14/git-practices/session-catchup"><img src="https://agentmods.dev/badge/commands/akshayrao14/git-practices/session-catchup.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 | $0.00040 | $0.00127 |
| Opus 5 | $0.00020 | $0.00063 |
| Sonnet 5 | $0.00008 | $0.00025 |
| Haiku 4.5 | $0.00004 | $0.00013 |
Grade A, and why
session-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 3d 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
Invoke the session-loop skill with focus=catchup. Load sub/catchup.md from the skill directory and follow it exactly.
Args (optional):
--focus <thread>— bias the recommendation toward a specific open thread from the handoff.
Replaces the built-in /resume (which loads a chat transcript, not project state). Acts on the current working directory's project.
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.
- 3d ago First seen · 12 lines · 40 tokens per session scan A 3d4e2edf7e18
session-catchup is a command published in the GitHub repository akshayrao14/git-practices (0 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 127 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-31.
Other commands, from other repositories
sonicjs-seo-blog
Generate a high-quality, SEO-optimized blog post for SonicJS on the topic: $ARGUMENTS.
upgrade-webkit
Upgrade Bun's WebKit fork to the latest upstream version of WebKit.
critique-pr
../../.mastracode/commands/critique-pr.md.
sm-sail
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
Q
MCP-first cross-validated code intelligence across dependency graphs.