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 Avijit07x/claude-db --skill catchupgit clone --depth 1 https://github.com/Avijit07x/claude-dbWrote 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/avijit07x/claude-db/catchup)<a href="https://agentmods.dev/skills/avijit07x/claude-db/catchup"><img src="https://agentmods.dev/badge/skills/avijit07x/claude-db/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/skills/avijit07x/claude-db/catchup"><img src="https://agentmods.dev/badge/skills/avijit07x/claude-db/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.00071 | $0.00601 |
| Opus 5.5 | $0.00028 | $0.00240 |
| Sonnet 5.5 | $0.00014 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade B, and why
catchup scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Do not save anything. Do not run any command that changes the repository. How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Where did I stop?
Run this from the project root:
claude-db catchup
It prints what memory and git know about this project, in plain text. Some parts may be missing. A part with nothing in it is left out.
Last handoffis a note the user or a teammate saved on purpose. Trust it most, unless its heading saysolder than the last chat. Then the last chat is newer, and wins where they differ.Not finished yet in another chatis a request another chat is still working on, or that was stopped. Say so under Open.Last chatandChat beforeare the other chats with the newest recorded requests, open or ended, newest first: the 5 newest requests in all.Still to doare to-dos found in earlier chats.Not committed yetis recorded work that no commit has covered.Decisions and dead endsare what was chosen or ruled out, with the reason.Branchsays which branch you are on and how many files are uncommitted.Git statusandRecent commitsare the live state of the repository.
If the output is Nothing recorded for this project yet., say exactly that and stop.
Answer in three groups
Reply with these three groups and nothing else. Keep each to a few short lines in plain words.
Done: what is finished. Take it from the last chat, the recent commits and the handoff's Done line.
Open: what is started but not finished. Take it from Not committed yet, Git status, the to-dos and the
handoff's Open line.
Next: what to do first. Take it from the handoff's Next line, then from the to-dos.
Rules
- Use only what the output shows. Do not read other files or search memory unless the user asks.
- Mark anything you are unsure of with
(guess). Never state a guess as a fact. - If there is no clear next step, write
No clear next step found.Do not invent one. - Say how old the information is. Use the dates in the output, for example
Last chat (Oct 6). - Do not save anything. Do not run any command that changes the repository.
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 Changed · +4 lines 8cacc95a1a3f
- 8d ago First seen · 47 lines · 71 tokens per session scan B b41ee438c6d6
catchup is a skill published in the GitHub repository Avijit07x/claude-db (234 stars, last pushed 5d ago), licensed Apache-2.0. It adds 71 tokens to every session and 601 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.
Other skills, from other repositories
repo-audit
Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets. Triggered when users ask about Git analysis, code hotspots, who owns what code, secret scanning, security audits of commit history, or optimizing code review assignments.
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.
commit-push-pr
Use when asked to commit and push a feature branch, with or without a pull request. Its no-PR mode publishes without a PR. Not for a PR body alone: use create-pull-request.
commit
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push-pr.
git-branchless
Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.
publish-branch
Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.