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 timheuer/copilot-instructions --skill vscode-extension-nbgvgit clone --depth 1 https://github.com/timheuer/copilot-instructionsWrote 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/timheuer/copilot-instructions/vscode-extension-nbgv)<a href="https://agentmods.dev/skills/timheuer/copilot-instructions/vscode-extension-nbgv"><img src="https://agentmods.dev/badge/skills/timheuer/copilot-instructions/vscode-extension-nbgv/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/timheuer/copilot-instructions/vscode-extension-nbgv"><img src="https://agentmods.dev/badge/skills/timheuer/copilot-instructions/vscode-extension-nbgv.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.00032 | $0.01105 |
| Opus 5 | $0.00016 | $0.00553 |
| Sonnet 5 | $0.00006 | $0.00221 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
vscode-extension-nbgv 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 10d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are going to help make changes to the package.json for a VS Code extension and also setup the GitHub Actions CI build workflow appropriately using automatic versioning with Nerdbank Git Versioning (NBGV).
Use the #askQuestions tool to ask any clarifying questions you need to ensure you can complete the task or for missing information.
Modifying package.json
The following needs to be ensured in the package.json file ONLY IF NOT SPECIFIED:
- version is: 0.0.0-placeholder
- author is needs to have a name and a url (ask if not known)
- publisher is the same as the Marketplace publisher name (ask if not known)
- icon is "icon.png" (validate this file exists and is at the root, summarize if it is not)
- repository is type 'git' with the URL of the remote repository of the workspace
- bugs property should be the /issues of the repository
- qna property should be the /issues of the repository
- in any workflow step that uses the Marketplace ID get that from the package.json
Ensuring scripts in package.json
These scripts should be defined in the package.json
- deploy: which is a 'vsce publish'
Build workflow
The build workflow should build the package, upload the artiface and publish to the marketplace using Nerdbank Git Versioning like so:
Example workflow:
name: Build and Publish
on:
workflow_dispatch:
branches:
- main
paths-ignore:
- '**/*.md'
- '**/*.gitignore'
- '**/*.gitattributes'
push:
branches:
- main
paths-ignore:
- '**/*.md'
- '**/*.gitignore'
- '**/*.gitattributes'
jobs:
build:
permissions:
contents: write
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: actions/setup-node@v4
with:
node-version: 20
- name: 📦 Install dependencies
run: npm install
- name: 🎁 Install vsce
run: npm install -g @vscode/vsce
- name: 🖥️ Install cross-env
run: npm install -g cross-env
- name: 🏷️ NBGV
uses: dotnet/nbgv@master
id: nbgv
with:
stamp: package.json
- name: 🗣️ NBGV outputs
run: |
echo "SimpleVersion: ${{ steps.nbgv.outputs.SimpleVersion }}"
- name: 📦 Package
run: |
vsce package -o ./${{ github.event.repository.name}}.vsix
- name: 📰 Publish
if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
run: npm run deploy
env:
VSCE_PAT: ${{ secrets.VSCE_PAT }}
- name: 🔗 Marketplace Link
if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
shell: pwsh
run: |
Write-Host "::notice::Published to VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=marketplace-id"
- name: ⬆️ Upload artifact
uses: actions/upload-artifact@v4
with:
name: ${{ github.event.repository.name}}.vsix
path: ./*.vsix
- name: 🏷️ Tag and Release
id: tag_release
uses: softprops/action-gh-release@v1
with:
body: Release ${{ steps.nbgv.outputs.SimpleVersion }}
tag_name: ${{ steps.nbgv.outputs.SimpleVersion }}
generate_release_notes: true
files: ./*.vsix
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.
- 10d ago First seen · 142 lines · 32 tokens per session scan A e28a74112f37
vscode-extension-nbgv is a skill published in the GitHub repository timheuer/copilot-instructions (1 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 1,105 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-08-31.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
start-temps-cluster
Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.