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/issue-grouping.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/issue-grouping)<a href="https://agentmods.dev/commands/microsoft/vscode/issue-grouping"><img src="https://agentmods.dev/badge/commands/microsoft/vscode/issue-grouping.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.00004 | $0.00355 |
| Opus 5 | $0.00002 | $0.00178 |
| Sonnet 5 | $0.00001 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
issue-grouping 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
Your Task
- Use a subagent to:
a. Using the GitHub MCP server, fetch only one page (50 per page) of the open issues for the given assignee and label in the
vscoderepository. b. After fetching a single page, look through the issues and see if there are are any good grouping categories.Output the categories as headers to a local file categorized-issues.md. Do NOT fetch more issue pages yet, make sure to write the categories to the file first. - Repeat step 1 (sequentially, don't parallelize) until all pages are fetched and categories are written to the file.
- Use a subagent to Re-fetch only one page of the issues for the given assignee and label in the
vscoderepository. Write each issue into the categorized-issues.md file under the appropriate category header with a link and the number of upvotes. If an issue doesn't fit into any category, put it under an "Other" category. - Repeat step 3 (sequentially, don't parallelize) until all pages are fetched and all issues are written to the file.
- Within each category, sort the issues by number of upvotes in descending order.
- Show the categorized-issues.md file as the final output.
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 · 23 lines · 4 tokens per session scan A cfccf311841a
issue-grouping is a command published in the GitHub repository microsoft/vscode (190,932 stars, last pushed today), licensed MIT. It adds 4 tokens to every session and 355 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
plugin-commands
:::info This document covers all build, test, and smoke commands for eIsland native plugins. Each plugin lives under plugins/ and has its own package.json with independent scripts. ::.
cloud-sdk-ai-chat-template
Generate or review a JavaScript or TypeScript chat template for SAP Cloud SDK for AI with safe configuration boundaries.
package-commands
:::info This document covers the packaging and lifecycle commands for building distributable installers and managing native modules. For development commands (dev, build, preview), see Development Commands. ::.
quality-commands
:::info This document covers the code quality commands for validating comment standards and i18n completeness in the eIsland frontend. ::.
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.