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 agentmods add skills/microsoft/vscode/update-screenshotsnpx skills add microsoft/vscode --skill update-screenshotsgit 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/update-screenshots)<a href="https://agentmods.dev/skills/microsoft/vscode/update-screenshots"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/update-screenshots.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 | $0.00060 | $0.01214 |
| Opus 5 | $0.00030 | $0.00607 |
| Sonnet 5 | $0.00012 | $0.00243 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
update-screenshots scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL -o old.png "https://hediet-screenshots.azurewebsites.net/images/<OLD_HASH>" How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Component Screenshots from CI
Screenshot images are not stored in the repository — they live in an external service
(hediet-screenshots.azurewebsites.net), keyed by commit SHA. But a subset of fixtures is
pinned by hash in test/componentFixtures/blocks-ci-screenshots.md,
and that file is committed. When those hashes change, CI fails and you must update the file.
Two different outcomes, only one of which blocks
The Screenshots & Tests job in .github/workflows/component-fixtures.yml
produces two independent results:
| Result | Blocking? | Action |
|---|---|---|
| Screenshot diff report (PR comment with before/after images) | No — informational | Review the visuals. Nothing to commit. |
| blocks-ci hash mismatch | Yes — fails the check | Update blocks-ci-screenshots.md and commit. |
A fixture opts into the blocking gate with labels: { kind: 'screenshot', blocksCi: true }.
Only those fixtures appear in blocks-ci-screenshots.md.
The failure looks like this:
##[error]blocks-ci screenshot hashes do not match committed file. See PR comment or job summary for the updated content.
Step 1: Get the expected hashes from CI
Never regenerate the hashes locally. They are hashes of the rendered PNG bytes, produced on
ubuntu-latest. Rendering on macOS or Windows yields different bytes and therefore different hashes, so locally generated values will fail CI. Always copy the values from the CI job.
Three surfaces carry the same content — use whichever is handy:
- The PR comment titled "blocks-ci screenshots changed" (non-fork PRs only) — contains the full updated file plus a patch.
- The job summary, which gets the identical body and is the only surface fork PRs receive.
- The job log, whose final step prints a unified diff:
gh api repos/microsoft/vscode/actions/jobs/<JOB_ID>/logs > "$TMPDIR/ci-job-log.txt"
grep -n '##\[error\]' "$TMPDIR/ci-job-log.txt"
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.
- yesterday First seen · 121 lines · 60 tokens per session scan A e16c09344118
update-screenshots is a skill published in the GitHub repository microsoft/vscode (190,863 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,214 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
run-openorbit
Build, run and drive the OpenOrbit Electron app. Use when asked to start the app, screenshot it, click through its UI, or confirm a change works in the real app rather than only in the test suite.
write-ui-tests
Creates UI tests for a GitHub issue and verifies they reproduce the bug. Iterates until tests actually fail (proving they catch the issue). Use when PR lacks tests or tests need to be created for an issue.
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
ux-acceptance-coordinator
Coordinate black-box, agent-driven UX acceptance journeys against a disposable EmDash admin site. Use when preparing, dispatching, verifying, or reporting a manual browser journey performed by a separate tester agent. Do not use for deterministic Playwright tests or ordinary code review.
ux-acceptance-tester
Perform a goal-driven, black-box UX acceptance journey in a browser and report the path, friction, and observable outcome. Use only in an isolated tester context with a supplied start URL and brief.
create-hotfix
Create a hotfix (patch) release branch for an Azure SDK Rust crate.