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/update-acumennpx skills add VGrss/Acumen --skill update-acumengit clone --depth 1 https://github.com/VGrss/AcumenWrote 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/vgrss/acumen/update-acumen)<a href="https://agentmods.dev/skills/vgrss/acumen/update-acumen"><img src="https://agentmods.dev/badge/skills/vgrss/acumen/update-acumen.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 | $0.00030 | $0.00645 |
| Opus 5 | $0.00015 | $0.00322 |
| Sonnet 5 | $0.00006 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
update-acumen 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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull the latest skills from the Acumen repo and sync them into this project.
Source repo: VGrss/Acumen on GitHub (branch: main)
Step 1: Fetch the current skill index from GitHub
Use gh to list the skill directories in the repo:
gh api repos/VGrss/Acumen/git/trees/main:source/skills --jq '.tree[] | select(.type == "tree") | .path'
This gives you the list of all skill names in the upstream repo.
Also list the local skills in source/skills/ to compare.
Report what's new, removed, or already present.
Step 2: Sync each skill's content
For every skill found upstream, fetch its files recursively. Each skill lives at source/skills/{name}/ and may contain SKILL.md plus optional subdirectories (e.g. reference/).
For each skill directory:
-
Get the file tree for that skill:
gh api repos/VGrss/Acumen/git/trees/main:source/skills/{name} --jq '.tree[]' -
For each file, fetch its raw content and write it locally:
gh api repos/VGrss/Acumen/contents/source/skills/{name}/{file} --jq '.content' | base64 -dWrite the decoded content to
source/skills/{name}/{file}. -
For subdirectories (like
reference/), recurse: list the subtree, then fetch each file inside it.
Step 3: Distribute to .agents and .claude
After syncing source/skills/, replicate the distribution structure:
-
Copy to
.agents/skills/: For each skill, copy the entiresource/skills/{name}/directory to.agents/skills/{name}/.cp -r source/skills/{name} .agents/skills/{name} -
Create
.claude/skills/symlinks: For any new skill that doesn't already have a symlink:ln -sf ../../.agents/skills/{name} .claude/skills/{name} -
Clean up removed skills: If a skill exists locally but not upstream, report it to the user and ask whether to remove it.
Step 4: Report
Print a summary:
- Updated: skills whose content changed
- Added: new skills not previously present locally
- Unchanged: skills that were already up to date
- Removed upstream (if any): skills present locally but missing from the repo — ask the user what to do
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.
- 4d ago First seen · 70 lines · 30 tokens per session scan A 68c80031acc7
update-acumen is a skill published in the GitHub repository VGrss/Acumen (11 stars, last pushed 29d ago), licensed Apache-2.0. It adds 30 tokens to every session and 645 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…