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 syncgit 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/sync)<a href="https://agentmods.dev/skills/microsoft/vscode/sync"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/sync.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.00052 | $0.00739 |
| Opus 5 | $0.00026 | $0.00369 |
| Sonnet 5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
sync 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Changes
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
Guidelines
- Never force-push (
--force,--force-with-lease) without explicit user approval. - Never skip pre-push hooks (do not use
--no-verify). - Never rewrite or drop commits during rebase without asking the user.
- When in doubt about conflict resolution — ask the user.
Workflow
- Check for uncommitted changes first. If there are uncommitted changes, use the
/commitskill to commit them before continuing. - Check whether the current session branch has an upstream branch.
- If the current session branch has an upstream branch:
3.1. Fetch the upstream remote first so tracking refs are up to date.
3.2. Check ahead/behind counts. If the branch is already in sync (0 ahead, 0 behind), stop and report that no sync is needed.git fetch <upstream-remote>
3.3. If behind, rebase onto the upstream tracking branch.git rev-list --left-right --count HEAD...@{u}
3.4. If there are merge conflicts, resolve them by preserving the intent of both sides. Stage the resolved files and continue the rebase.git rebase @{u}
If conflict resolution is unclear, ask the user how to proceed. If the user wants to stop the rebase, abort it:git add <resolved-files> git rebase --continue
3.5. If the branch has local commits (ahead > 0), push them to the remote after a successful rebase.git rebase --abort
If the push is rejected because the rebase rewrote history, explain the situation to the user and ask for approval before force-pushing.git push - If the current session branch does not have an upstream branch:
4.1. Determine the remote to publish to.
- If there is only one remote, use it.
- If there are multiple remotes, use the #tool:vscode/askQuestions tool to ask which remote to use. 4.2. Publish the current branch and set upstream in one step.
git push -u <remote> HEAD
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 · 74 lines · 52 tokens per session scan A db06725499cf
sync is a skill published in the GitHub repository microsoft/vscode (191,195 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 739 once invoked, about $0.0003 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.
merge-seed
Merge upstream React Starter Kit updates (the seed remote) into main, preserving this project's identity, scope, and behavior. Use when asked to sync, pull, or merge the seed / starter kit / upstream template.
om-auto-implement-spec
Everything tracker-facing uses the operations and guards from .ai/trackers/github.md. Resolve an automatic base branch through default-branch; never assume main or develop.
cyrene-work-hygiene
A Work-mode rulebook for organizing projects that create, arrange, or deliver several files.
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.