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/sweeper-plan/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/sweeper-plan)<a href="https://agentmods.dev/skills/microsoft/vscode/sweeper-plan"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/sweeper-plan/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/sweeper-plan"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/sweeper-plan.svg" alt="Reviewed on agentmods" width="80" 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.00142 | $0.02446 |
| Opus 5.5 | $0.00057 | $0.00978 |
| Sonnet 5.5 | $0.00028 | $0.00489 |
| Haiku 4.5 | $0.00014 | $0.00245 |
Grade A, and why
sweeper-plan 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sweeper-plan — plan a sweeper-reviewed issue with the maintainer
You are working on a single microsoft/vscode issue on behalf of the maintainer who invoked you. The VS Code Sweeper reviewed it and judged it agent-ready — usually plan: the goal is clear but the review left the diagnosis or the design open (open decisions, a multi-system scope, or a reproduction it could not confirm). A maintainer may also plan an implement record deliberately.
Your job ends with a plan file, .sweeper/plans/issue-<issue-number>.md, written WITH the maintainer — never code. The maintainer edits the file in their editor and then runs /sweeper-implement <issue-number>, which implements the approved plan and opens the draft PR.
Keep the chat short: the maintainer reads the plan in their editor, not pasted into the conversation. Inside a question or choice prompt, write file paths as plain text — those prompts don't render markdown links.
0 · Preconditions (refuse if unmet)
- The working directory must be a microsoft/vscode checkout —
git remote -vmust listmicrosoft/vscode. If not, stop: "run this from your vscode checkout". - The checkout must have no tracked modifications and no staged changes (
git status --porcelain, ignoring untracked files). Dirty → stop and say so; do NOT stash, discard, or commit the maintainer's work-in-progress. Untracked files may stay — the ship step commits only files this skill created or edited. gh auth statusmust succeed (the gates and the PR need it).
1 · Fetch the review record
The issue number comes from the maintainer's request. Fetch the record (public, no special access):
gh api "repos/egamma/vscodesweeper-state/contents/records/microsoft/vscode/items/<issue-number>.md?ref=state" -H "Accept: application/vnd.github.raw"
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 Changed · -74 lines 99e3b27cb88f
- 20d ago First seen · 180 lines · 142 tokens per session scan A 5ed7a4c869c6
sweeper-plan is a skill published in the GitHub repository microsoft/vscode (193,657 stars, last pushed today), licensed MIT. It adds 142 tokens to every session and 2,446 once invoked, about $0.0006 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-26.
Other skills, from other repositories
triage
Classify an issue, identify missing information, and decide whether bounded automatic work is safe.
record-gotchas
Capture surprises, workarounds, and rough edges hit while consuming the public surface of Prisma 8, Prisma Compute, or Prisma Postgres — anything a real user of these products would experience. Fires whenever an operator (or agent) writes a workaround, hits a surprising failure mode, or finds undocumented behaviour…
resolution_playbook
How to choose one resolution action from a ticket and its customer history.
stacking-prs
Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…
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.