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-promptgit 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-prompt)<a href="https://agentmods.dev/skills/microsoft/vscode/create-prompt"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/create-prompt.svg" alt="Measured on agentmods" height="20"></a>- Snyk 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.00262 |
| Opus 5 | $0.00009 | $0.00131 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
create-prompt 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 3d 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 prompts.md for template and principles.
Guide the user to create a .prompt.md.
Extract from Conversation
First, review the conversation history. If the user has been working on a repeatable task pattern (e.g., explaining code, generating tests, refactoring), generalize that into a reusable prompt. Extract:
- The core task being performed repeatedly
- Any implicit inputs (selected code, file type, context)
- The desired output format or style
Clarify if Needed
If no clear pattern emerges from the conversation, clarify:
- What task should this prompt help with?
- Should it take arguments or use fixed context?
- Workspace-scoped or personal?
Iterate
- Draft the prompt and save it.
- Identify the most ambiguous or weak parts and ask about those.
- Once finalized, summarize what the prompt does, suggest example invocations, and propose related customizations to create next.
Remember to follow the agent-customization guidelines to create highly effective prompts.
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.
- 3d ago First seen · 29 lines · 18 tokens per session scan A 19ef799ca243
create-prompt is a skill published in the GitHub repository microsoft/vscode (191,195 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 262 once invoked, about $0.0001 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-09-03.
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-work-hygiene
A Work-mode rulebook for organizing projects that create, arrange, or deliver several files.
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-learn-tutor
A Chinese-language tutoring process for helping users understand study materials, practise concepts, and track learning progress.
cyrene-original-voice
A writing-style calibration that changes responses to match the voice of the character 昔涟 when certain conversation situations are detected. It supplies tone rules and example responses.