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/webdevtodayjason/titanium-plugins/catchupgit clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWhat 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.00014 | $0.00262 |
| Opus 5 | $0.00007 | $0.00131 |
| Sonnet 5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
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 yesterday.
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
You are starting a new session with the user. Use the Pieces MCP ask_pieces_ltm tool to gather context about:
- What projects the user has been working on recently (last 24-48 hours)
- What specific tasks or files they were editing
- Any unfinished work or issues they encountered
- The current state of their active projects
Query Pieces with questions like:
- "What projects has the user been working on in the last 24 hours?"
- "What was the user working on most recently?"
- "What files or code was the user editing recently?"
- "Were there any errors or issues the user was troubleshooting?"
After gathering this context, provide a concise summary organized by:
- Active Projects: List the main projects with brief descriptions
- Recent Work: What was being worked on most recently
- Where We Left Off: Specific tasks, files, or issues that may need continuation
- Current Focus: What appears to be the highest priority based on recent activity
Be specific with file paths, timestamps, and concrete details. The goal is to help both you and the user quickly resume work without losing context.
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.
- yesterday First seen · 25 lines · 14 tokens per session scan A 0991ca109493
catchup is a command published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 262 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.