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 skills/vgrss/acumen/catchupnpx skills add VGrss/Acumen --skill catchupgit clone --depth 1 https://github.com/VGrss/AcumenWhat 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.00048 | $0.01448 |
| Opus 5 | $0.00024 | $0.00724 |
| Sonnet 5 | $0.00010 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Product people working on top of a codebase need to stay current with what engineers shipped — without risking the product context they've built up. This skill pulls the latest code and translates recent changes into product language.
Step 1: Protect product context
Before touching anything, confirm that product context files are safe:
- Check that
.acumen.md,.acumen/, and any other product context files exist and are gitignored - If any product context files are tracked by git (not gitignored), stop and warn the user — those files could be overwritten by a pull
List the protected files found and confirm they're safe.
Step 2: Pull latest code
- Check for uncommitted changes with
git status. If there are local changes to tracked files:- Run
git stashto save them - Note that changes were stashed so you can report this later
- Run
- Pull from main:
git pull origin main - If there were stashed changes, run
git stash popand report any conflicts.
Step 3: Summarize what changed
Determine the time range:
- If the user provided a
[since]argument (e.g., "last week", "since Monday", "3 days"), use it - Otherwise, use the last time the user could have synced — check
git reflog show --date=relativefor the previous pull, or default to last 7 days
Gather changes
git log --since="<date>" --merges --oneline
git log --since="<date>" --no-merges --oneline
Also check for recently merged PRs if gh is available:
gh pr list --state merged --limit 20 --json number,title,body,mergedAt,author
Write the summary
Organize changes into a product-friendly summary. Do NOT just list commits — translate them:
- What shipped — new capabilities, visible changes, things users/stakeholders would notice
- What improved — performance, reliability, UX refinements
- What was fixed — bugs that were resolved
- Under the hood — refactors, infra, CI changes (keep brief, 1-2 lines max)
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 · 149 lines · 48 tokens per session scan A 861736ca65f2
catchup is a skill published in the GitHub repository VGrss/Acumen (11 stars, last pushed 26d ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,448 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.