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.
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 microsoft/vscode --skill create-hookgit 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/create-hook)<a href="https://agentmods.dev/skills/microsoft/vscode/create-hook"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/create-hook/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/create-hook"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/create-hook.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.00018 | $0.00399 |
| Opus 5.5 | $0.00007 | $0.00160 |
| Sonnet 5.5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
create-hook 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 2mo 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.
What it actually says
Related skill: agent-customization. Load and follow hooks.md for template and principles.
Guide the user to create a hook in .github/hooks/.
Extract from Conversation
First, review the conversation history. If the user has been expressing concerns about agent behavior (e.g., "don't run this command", "always check before doing X", "inject this context"), generalize that into a hook. Extract:
- Actions that should be blocked or gated
- Context that should be injected at certain points
- Automation needs at session start/end or tool use
Clarify if Needed
If no clear policy need emerges from the conversation, clarify:
- What event should trigger this hook? (e.g. PreToolUse, SessionStart, Stop)
- Should it block, warn, or inject context?
- Does it need a companion script?
Path Conventions
- Hook commands and companion scripts run with
cwddefaulting to the workspace root (when a workspace folder is available); otherwisecwdfalls back to the user home directory. Relative paths resolve fromcwd. Absolute paths are fine when intentional — just be deliberate about which you use. - Do not use environment variables for pathing. The only exception is plugin-provided environment variables in hooks shipped as part of an agent plugin; never use environment variables for pathing outside of a plugin context.
Iterate
- Draft the hook JSON (and any scripts) and save them.
- Identify the most ambiguous or weak parts and ask about those.
- Once finalized, summarize what the hook enforces, suggest ways to test it, and propose related customizations to create next.
Remember to follow the agent-customization guidelines to create highly effective hooks.
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.
- 2mo ago First seen · 33 lines · 18 tokens per session scan A 90ffcc7d0b6d
create-hook is a skill published in the GitHub repository microsoft/vscode (195,109 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 399 once invoked, about $0.0001 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-09-03.
create-hook compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| create-hookmicrosoft/vscode | Skill | 195k | today | MIT | A | 18 | Claude Code |
| cyrene-plan-modePlaya-0v0/Cyrene-Agent | Skill | 597 | 1mo ago | MIT | A | 37 | Claude Code, Codex |
| cyrene-plugin-devPlaya-0v0/Cyrene-Agent | Skill | 597 | 1mo ago | MIT | A | 61 | Claude Code, Codex |
| cyrene-exam-paperPlaya-0v0/Cyrene-Agent | Skill | 597 | 1mo ago | MIT | A | 64 | Claude Code, Codex |
| cyrene-work-hygienePlaya-0v0/Cyrene-Agent | Skill | 597 | 1mo ago | MIT | A | 56 | Claude Code, Codex |
| cyrene-obsidian-workspacePlaya-0v0/Cyrene-Agent | Skill | 597 | 1mo ago | MIT | A | 42 | Claude Code, Codex |
| cyrene-diagramPlaya-0v0/Cyrene-Agent | Skill | 597 | 1mo ago | MIT | A | 50 | Claude Code, Codex |