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/zenml-io/zenml/catchupgit clone --depth 1 https://github.com/zenml-io/zenmlWhat 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.00009 | $0.00135 |
| Opus 5 | $0.00005 | $0.00068 |
| Sonnet 5 | $0.00002 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
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 2d 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 current branch changes
! git diff --name-only $(git merge-base HEAD origin/develop)
Please read all the files listed above that were changed in this branch compared to the base branch (develop). For each file:
- Use the
viewtool to read its contents - Provide a brief summary of what changed
After reviewing all files, give me a concise summary of:
- What areas of the codebase were modified
- The overall purpose/theme of these changes
- Any potential concerns or questions I should be aware of
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.
- 2d ago First seen · 19 lines · 9 tokens per session scan A b27f24219e05
catchup is a command published in the GitHub repository zenml-io/zenml (5,572 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 135 once invoked, about $0.0000 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
pre-pr
Run the full OpsML test suite (Rust + Python) before submitting a PR. Capture and report all errors clearly at each step. Stop a workflow only if a step produces errors that would block the next step from running correctly.
add-task-module
Scaffold a new task module (classification/regression/clustering/...).
run-engine-tests
Fast local test loop for the engine package.
ds-learn
Capture a failure-and-fix pair as a project lesson.
ds
Show the Last DS Mile pipeline map and which stage comes next.
ds-brief
Rewrite the results as a one-page brief with no jargon.