Visual Studio Code is a code editor that supports editing, navigating, understanding, debugging, and extending software projects. Developers use it for the edit-build-debug cycle, and the catalogue add-ons provide skills, instructions, and agents for working within the editor.
Borrowing it
Nothing to install: this file belongs to microsoft/vscode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/vscode/main/.github/skills/cpu-profile-analysis/SKILL.mdgit clone --depth 1 https://github.com/microsoft/vscodeWrote 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/microsoft/vscode/cpu-profile-analysis)<a href="https://agentmods.dev/skills/microsoft/vscode/cpu-profile-analysis"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/cpu-profile-analysis/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/microsoft/vscode/cpu-profile-analysis"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/cpu-profile-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.05847 |
| Opus 5.5 | $0.00028 | $0.02339 |
| Sonnet 5.5 | $0.00014 | $0.01169 |
| Haiku 4.5 | $0.00007 | $0.00585 |
Grade A, and why
cpu-profile-analysis 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 1mo 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 — 518 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Performance Profiles
Analyze .cpuprofile files (V8 sampling profiler) and DevTools trace files (Trace-*.json, Chrome Trace Event Format) to find performance bottlenecks, compare code paths, and understand timing.
When to Use
- User provides a
.cpuprofileorTrace-*.jsonfile and wants to understand performance - Investigating why one code path is slower than another
- Finding what functions consume the most time
- Comparing "before/after" or "old/new" implementations in a single profile
- Investigating layout thrashing, long tasks, or rendering bottlenecks (trace files)
- Analyzing VS Code user timing marks like
code/didResolveTextFileEditorModel(trace files) - Understanding multi-process behavior (Browser, Renderer, GPU processes in trace files)
Detecting File Type
.cpuprofile: Top-level JSON withnodes,samples,timeDeltaskeys. Created by the VS Code profiler.Trace-*.json: Top-level JSON withtraceEventsarray (and optionalmetadata). Created by Chrome/Electron DevTools (Performance tab). These are richer than.cpuprofile-- they contain CPU samples, layout/paint events, user timing marks, GC events, input events, and multi-process data.
Key Concepts
- Sampling profiler: The profiler periodically snapshots the call stack. Not every function appears -- only those on the stack when the profiler sampled. Don't expect exact function names; look for patterns and nearby activity.
- Self time: Time spent in the function itself (the leaf/innermost frame).
- Total time: Time the function was anywhere on the stack (includes callees).
- Idle samples: Frames labeled
(idle),(program), or(garbage collector)represent no user code running.
Part 1: .cpuprofile Files
Profile Format
A .cpuprofile is JSON with these top-level keys:
nodes: Array of call frame nodes forming a tree (each hasid,callFrame,children)samples: Array of node IDs -- one per profiler tick, referencing the leaf (innermost) frametimeDeltas: Array of microsecond deltas between consecutive samplesstartTime/endTime: Absolute timestamps in microseconds$vscode: Optional VS Code metadata
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.
- 1mo ago First seen · 518 lines · 71 tokens per session scan A 73e7d3ba6ff8
cpu-profile-analysis is a skill published in the GitHub repository microsoft/vscode (193,839 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 5,847 once invoked, about $0.0003 per session on Opus 5.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
cyrene-plan-mode
A planning guide for Cyrene’s Plan Mode, used before code or file changes are made. It helps turn a broad request into an agreed implementation plan based on the project’s actual code and constraints.
cyrene-plugin-dev
A guide for developing runtime plugins for Cyrene, including plugins that add tools, windows, events, live context, or connections to services. Cyrene is the host application that runs these plugins.
cyrene-exam-paper
A method for creating formal exams from a learning plan, then keeping the questions, answers, grading, and review separate. It maps learned topics to skills and suitable question types.
cyrene-obsidian-workspace
A set of rules for an agent working with an Obsidian vault, a folder of linked Markdown notes. It defines where materials, notes, exercises, templates, and progress files belong and how they may be edited.
cyrene-work-hygiene
A Work-mode rulebook for organizing projects that create, arrange, or deliver several files.
cyrene-diagram
A design guide for making static SVG learning cards: small diagrams or reference cards rendered as images. It explains when to use a card instead of Mermaid, a text-based diagram format, and sets layout, color, size, and safety rules.