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/codenotify/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/codenotify)<a href="https://agentmods.dev/skills/microsoft/vscode/codenotify"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/codenotify/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/codenotify"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/codenotify.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.00007 | $0.00841 |
| Opus 5.5 | $0.00003 | $0.00336 |
| Sonnet 5.5 | $0.00001 | $0.00168 |
| Haiku 4.5 | $0.00001 | $0.00084 |
Grade A, and why
codenotify 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add My Contributions to CODENOTIFY
This prompt helps you add your code contributions to the .github/CODENOTIFY file based on git blame history.
Instructions
Before running this prompt, provide the following information:
- Your GitHub handle: (e.g.,
@YOURHANDLE) - Alternative usernames in git blame: (e.g.,
Erich Gamma,[email protected], or any other names/emails that might appear in git commits)
What This Prompt Does
This prompt will:
- Search through the repository's git blame history for files you've significantly contributed to
- Analyze which files and directories have your contributions
- Follow the existing structure in the
.github/CODENOTIFYfile, here are some examples:src/vs/base/common/**→ Add to Base Utilities sectionsrc/vs/base/browser/ui/**→ Add to Base Widgets sectionsrc/vs/base/parts/**→ Add to Base Utilities sectionsrc/vs/platform/**→ Add to Platform sectionsrc/bootstrap-*.ts,src/main.ts, etc. → Add to Bootstrap sectionsrc/vs/code/**→ Add to Electron Main sectionsrc/vs/workbench/services/**→ Add to Workbench Services sectionsrc/vs/workbench/common/**,src/vs/workbench/browser/**→ Add to Workbench Core sectionsrc/vs/workbench/contrib/**→ Add to Workbench Contributions sectionsrc/vs/workbench/api/**→ Add to Workbench API sectionextensions/**→ Add to Extensions section
- Add appropriate entries in the format:
- Individual files:
path/to/file.ts @yourusername - Directories:
path/to/directory/** @yourusername
- Individual files:
- Place entries within existing sections, maintaining alphabetical or logical order
- Create new sections only if contributions don't fit existing categories
- Avoid duplicating existing entries
Expected Output Format
Entries will be added to existing sections based on their path. For example:
# Base Utilities
src/vs/base/common/extpath.ts @bpasero
src/vs/base/common/oauth.ts @yourusername # ← Your contribution added here
src/vs/base/parts/quickinput/** @yourusername # ← Your contribution added here
# Platform
src/vs/platform/quickinput/** @yourusername # ← Your contribution added here
src/vs/platform/secrets/** @yourusername # ← Your contribution added here
# Workbench Services
src/vs/workbench/services/authentication/** @yourusername # ← Your contribution added here
# Workbench Contributions
src/vs/workbench/contrib/authentication/** @yourusername # ← Your contribution added here
src/vs/workbench/contrib/localization/** @yourusername # ← Your contribution added here
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 · 82 lines · 7 tokens per session scan A 2446a81a4fef
codenotify is a skill published in the GitHub repository microsoft/vscode (193,657 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 841 once invoked, about $0.0000 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
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.
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
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.
competitor-product-monitor
Monitor competitor product releases and new feature announcements. Use this skill when the user wants to track what competitors are shipping, find the latest product launches in their industry, or generate a competitor release report. Triggers include phrases like "track competitor releases", "what are my competitors…