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 TheWinci/mimirs --skill catch-upgit clone --depth 1 https://github.com/TheWinci/mimirsWrote 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/thewinci/mimirs/catch-up)<a href="https://agentmods.dev/skills/thewinci/mimirs/catch-up"><img src="https://agentmods.dev/badge/skills/thewinci/mimirs/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.00061 | $0.00259 |
| Opus 5 | $0.00030 | $0.00130 |
| Sonnet 5 | $0.00012 | $0.00052 |
| Haiku 4.5 | $0.00006 | $0.00026 |
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 7d 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
Catch-up
Goal: rebuild context on the current state — not the whole codebase (that's explore).
- What's changed —
git_contextfor modified/uncommitted files, recent commits, and which changed files are in the index. - Recent decisions —
list_checkpointsfor the latest checkpoints;search_checkpoints "<area you're resuming>"for ones relevant to the task. - Open caveats —
get_annotationson the changed files for known bugs, constraints, or "don't touch until X" notes left earlier. - Prior discussion —
search_conversation "<task/area>"to recall what was being worked on and any unresolved threads.
Finish: a short status — what changed, what's in flight, decisions/caveats affecting the next step — with file:line and checkpoint references. Confirm the plan before continuing.
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.
- 7d ago First seen · 16 lines · 61 tokens per session scan A a808df67cc8a
catch-up is a skill published in the GitHub repository TheWinci/mimirs (29 stars, last pushed 22d ago), licensed Apache-2.0. It adds 61 tokens to every session and 259 once invoked, about $0.0003 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
monday-webhooks
Receive and verify monday.com webhooks. Use when setting up monday.com webhook handlers, implementing the challenge handshake, debugging JWT verification, or handling board events like createitem, changecolumnvalue, changestatuscolumnvalue, createupdate, or createsubitem.
status
Show a comprehensive project status dashboard: task queue, blocked items, session state, verification, and git status.
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…