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-implement/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-implement)<a href="https://agentmods.dev/skills/microsoft/vscode/sweeper-implement"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/sweeper-implement/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-implement"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/sweeper-implement.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.00187 | $0.03398 |
| Opus 5.5 | $0.00075 | $0.01359 |
| Sonnet 5.5 | $0.00037 | $0.00680 |
| Haiku 4.5 | $0.00019 | $0.00340 |
Grade A, and why
sweeper-implement 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sweeper-implement — implement a sweeper-reviewed issue
You are working on a single microsoft/vscode issue on behalf of the maintainer who invoked you. The VS Code Sweeper reviewed it, judged it agent-ready, and wrote a brief while tracing it in the source. You implement the issue and end in a draft PR the maintainer owns. What you implement from depends on the record's tier:
implementrecord → the brief. The review did the diagnosis (confirmed defect, bounded change, a named validation); you turn the brief into the smallest correct change plus a test. There is no plan file (Sweeper mode: implement).planrecord → the approved plan file,.sweeper/plans/issue-<issue-number>.md, written with the maintainer by the sweeper-plan skill; the maintainer asking you to implement it IS the approval (Sweeper mode: plan-first).
Below, the spec means whichever of the two you are working from. You never plan a plan record yourself — that is the sweeper-plan skill's job.
Keep the chat short: the maintainer reads the spec and the diff 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).
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 · -104 lines 45939d067ac5
- 20d ago First seen · 235 lines · 187 tokens per session scan A 0f8638697895
sweeper-implement is a skill published in the GitHub repository microsoft/vscode (193,657 stars, last pushed today), licensed MIT. It adds 187 tokens to every session and 3,398 once invoked, about $0.0007 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
open-code-review
Use Alibaba Open Code Review (ocr) to review git diffs, staged changes, branches, or scan a workspace, then summarize findings and optionally fix high-confidence issues.
Release Readiness
Review a change against release gates, rollback safety, validation evidence, and operational risk.
performance-lint-rules
Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
qa-frontend
Internal PostHog developer frontend/browser QA skill. Use only when a PostHog developer explicitly asks to run frontend QA, browser-test a PR, verify a UI flow against the local PostHog stack, use qa-frontend, or QA current frontend changes with browser/runtime evidence, or to make a feature reel (see reel mode…
quick-merge
Identify trivial, low-risk PRs in the ready for maintainer review queue of that pass every quality gate and touch only supplementary areas (docs, changelog, translations, tests) — the "express lane". Surfaces and ranks candidates with per-PR diff summaries, an all-gates-green attestation, and the exact merge command.…