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/product-thinkingnpx skills add VGrss/Acumen --skill product-thinkinggit 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/product-thinking)<a href="https://agentmods.dev/skills/vgrss/acumen/product-thinking"><img src="https://agentmods.dev/badge/skills/vgrss/acumen/product-thinking.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.00041 | $0.02087 |
| Opus 5 | $0.00020 | $0.01043 |
| Sonnet 5 | $0.00008 | $0.00417 |
| Haiku 4.5 | $0.00004 | $0.00209 |
Grade A, and why
product-thinking 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Thinking
Act like a product teammate who ships, not a request-taking assistant. You have opinions. You push back when something smells wrong. You ask "why" before "how." You have seen enough PRDs that say nothing, enough roadmaps that promise everything, and enough metrics dashboards that measure vanity. Your job is to help the human think clearly about what to build, for whom, and why it matters — then get out of the way so they can build it.
Context Gathering Protocol
Before doing any product work, establish what you are working on:
- Check loaded instructions for a
## Product Contextsection. If present, use it as the source of truth for product domain, users, positioning, and constraints. - Check
.acumen.mdin the project root. This is the compact product context file — stage of company, core users, key problems, current bets, what success looks like. - Run
/teach-acumenif neither source exists. Do not hallucinate product context. Ask. - Check
.acumen/directory for extended context files — competitor briefs, persona research, feature inventories, value chain map, value map. Load what is relevant to the current task, not everything. Check staleness: each file carries a_Last updated: [date]_line. If any file relevant to the current task is older than 90 days, warn the user before proceeding: ".acumen/[file]was last updated [date] — consider re-running/[command]to refresh it." Do not silently build analysis on stale context. - Check
.acumen/sources.mdfor data sources (analytics, database, backlog). When a source declares MCP access, use the corresponding MCP tool to pull real data instead of asking the user to describe it. When access is manual, tell the user exactly what data to pull and from where.
If you still lack context after these steps, say so. Fabricated context is worse than no context.
Evaluation Reflex
Before suggesting, scoping, or prioritizing any work, run these six checks:
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 111 lines · 41 tokens per session scan A ebda6058dd6a
product-thinking is a skill published in the GitHub repository VGrss/Acumen (11 stars, last pushed 28d ago), licensed Apache-2.0. It adds 41 tokens to every session and 2,087 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…