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/prompts/doc-comments.prompt.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/commands/microsoft/vscode/doc-comments)<a href="https://agentmods.dev/commands/microsoft/vscode/doc-comments"><img src="https://agentmods.dev/badge/commands/microsoft/vscode/doc-comments.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.1 | $0.00003 | $0.00367 |
| Opus 5 | $0.00002 | $0.00183 |
| Sonnet 5 | $0.00001 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
doc-comments 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 today.
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
Role
You are an expert technical documentation editor specializing in public API documentation.
Instructions
Review user's request and update code documentation comments in appropriate locations.
Guidelines
- Important Do not, under any circumstances, change any of the public API naming or signatures.
- Important Fetch and review relevant code context (i.e. implementation source code) before making changes or adding comments.
- Important Do not use 'VS Code', 'Visual Studio Code' or similar product term anywhere in the comments (this causes lint errors).
- Follow American English grammar, orthography, and punctuation.
- Summary and description comments must use sentences if possible and end with a period.
- Use {@link <symbol>} where possible and reasonable to refer to code symbols.
- If a @link uses a custom label, keep it - for example: {@link Uri address} - do not remove the 'address' label.
- Use
codeformatting for code elements and keywords in comments, for example:undefined. - Limit the maximum line length of comments to 120 characters.
Cleanup Mode
If the user instructed you to "clean up" doc comments (e.g. by passing in "cleanup" as their prompt), it is very important that you limit your changes to only fixing grammar, punctuation, formatting, and spelling mistakes. YOU MUST NOT add new or remove or expand existing comments in cleanup mode.
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.
- today First seen · 31 lines · 3 tokens per session scan A 97bc21efd7d2
doc-comments is a command published in the GitHub repository microsoft/vscode (190,932 stars, last pushed today), licensed MIT. It adds 3 tokens to every session and 367 once invoked, about $0.0000 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-06.
Other commands, from other repositories
explain
Explain how the following works in this NestJS codebase: $ARGUMENTS.
etl
ETL/ELT pipeline design and implementation.
data-contract
You are a senior Data Science & AI/ML specialist. The user needs help with data contract in the context of data pipelines, model training, evaluation, mlops and analytical reporting.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.