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/migrate-issues/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/migrate-issues)<a href="https://agentmods.dev/skills/microsoft/vscode/migrate-issues"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/migrate-issues/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/migrate-issues"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/migrate-issues.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.00015 | $0.01209 |
| Opus 5.5 | $0.00006 | $0.00484 |
| Sonnet 5.5 | $0.00003 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
migrate-issues 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 27d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Migration Prompt
Use this prompt when migrating issues from one GitHub repository to another (e.g., from microsoft/vscode-copilot to microsoft/vscode).
Input Methods
You can specify which issues to migrate using any of these three methods:
Option A: GitHub Search Query URL
Provide a full GitHub issues search URL. All matching issues will be migrated.
https://github.com/microsoft/vscode-copilot/issues?q=is%3Aissue+is%3Aopen+assignee%3Ayoyokrazy
Option B: GitHub Search Query Parameters
Provide search query syntax for a specific repo. All matching issues will be migrated.
repo:microsoft/vscode-copilot is:issue is:open assignee:yoyokrazy
Common query filters:
is:issue/is:pr- Filter by typeis:open/is:closed- Filter by stateassignee:USERNAME- Filter by assigneeauthor:USERNAME- Filter by authorlabel:LABEL- Filter by labelmilestone:MILESTONE- Filter by milestone
Option C: Specific Issue URL
Provide a direct link to a single issue. Only this issue will be migrated.
https://github.com/microsoft/vscode-copilot/issues/12345
Task
Target Repository: {TARGET_REPO}
Based on the input provided, migrate the issue(s) to the target repository following all requirements below.
Requirements
1. Issue Body Format
Create the new issue with this header format:
_Transferred from {SOURCE_REPO}#{ORIGINAL_ISSUE_NUMBER}_
_Original author: `@{ORIGINAL_AUTHOR}`_
---
{ORIGINAL_ISSUE_BODY}
2. Comment Migration
For each comment on the original issue, add a comment to the new issue:
_`@{COMMENT_AUTHOR}` commented:_
---
{COMMENT_BODY}
3. CRITICAL: Preventing GitHub Pings
ALL @username mentions MUST be wrapped in backticks to prevent GitHub from sending notifications.
✅ Correct: `@username`
❌ Wrong: @username
This applies to:
- The "Original author" line in the issue body
- Any
@mentionswithin the issue body content - The comment author attribution line
- Any
@mentionswithin comment content - Any quoted content that contains
@mentions
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.
- 27d ago First seen · 174 lines · 15 tokens per session scan A e3d5256c8aaa
migrate-issues is a skill published in the GitHub repository microsoft/vscode (193,657 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,209 once invoked, about $0.0001 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-19.
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.