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 skills add microsoft/vscode --skill act-on-feedbackgit 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/act-on-feedback)<a href="https://agentmods.dev/skills/microsoft/vscode/act-on-feedback"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/act-on-feedback.svg" alt="Measured on agentmods" height="20"></a>- Snyk pass
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.00031 | $0.00217 |
| Opus 5 | $0.00015 | $0.00109 |
| Sonnet 5 | $0.00006 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
act-on-feedback 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.
What it actually says
Act on Feedback
The user has provided feedback on the current session's changes.
- Use the
listCommentstool to retrieve the user's feedback comments for this session - If specific feedback comments were attached to this message, act on only those attached comments (match them by their comment id); otherwise act on all of the listed comments, or whatever subset the user specified in their message
- Understand the intent behind each piece of feedback you are acting on
- Make the requested changes to address the feedback
- When feedback has been tackled, use the
resolveCommentstool to mark those comments as resolved, or thedeleteCommentstool to delete them - Verify your changes are consistent with the rest of the codebase
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 First seen · 17 lines · 31 tokens per session scan A 9ef138b532eb
act-on-feedback is a skill published in the GitHub repository microsoft/vscode (191,195 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 217 once invoked, about $0.0002 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-03.
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.
remember
Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture…
code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
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.
cyrene-work-hygiene
A Work-mode rulebook for organizing projects that create, arrange, or deliver several files.