What is build-vscode-extension?

A command for building and locally installing a Visual Studio Code extension, which adds features to the VS Code editor. It runs dependency installation, linting, compilation, tests, packaging, and installation in order.

Use it to validate the extension, create its installable VSIX package, install it in VS Code, and confirm that the editor is ready for reloading.

It gives the project a repeatable local check and stops when a build step fails, making problems easier to identify before inspection or distribution.

build-vscode-extension — Command for Claude Code by untra: A command for building and locally installing a Visual…

Install

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.

agentmods

npx agentmods add commands/untra/operator/build-vscode-extension

Clone the repo

git clone --depth 1 https://github.com/untra/operator

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/untra/operator/build-vscode-extension.svg)](https://agentmods.dev/commands/untra/operator/build-vscode-extension)

Your own site

<a href="https://agentmods.dev/commands/untra/operator/build-vscode-extension"><img src="https://agentmods.dev/badge/commands/untra/operator/build-vscode-extension.svg" alt="Measured on agentmods" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 382 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00015	$0.00382
Opus 5	$0.00008	$0.00191
Sonnet 5	$0.00003	$0.00076
Haiku 4.5	$0.00002	$0.00038

Measured 3d ago against content hash 8981644d5ea4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

build-vscode-extension 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.

.claude/commands/build-vscode-extension.md · 29 lines

What it actually says

Build VS Code Extension

Build, validate, package, and install the vscode-extension subproject for local inspection. Stop immediately on any failure and report the error.

Workflow

Run each step sequentially from the vscode-extension/ directory. If any step fails, stop and report the failure clearly.

Install dependencies: cd vscode-extension && npm install
Lint: cd vscode-extension && npm run lint
Compile: cd vscode-extension && npm run compile
Test: cd vscode-extension && npm test (note: requires a display environment for @vscode/test-electron; if tests fail due to missing display, report it and continue)
Package: cd vscode-extension && npm run package (creates a .vsix file via vsce)
Detect version: cd vscode-extension && node -p "require('./package.json').version"
Install extension: cd vscode-extension && code --install-extension ./operator-terminals-VERSION.vsix (substitute the detected version)
Report: Confirm the extension was installed successfully. Remind the user they must reload their VS Code window (Developer: Reload Window from the command palette) for changes to take effect.

Notes

The npm run compile step runs copy-types then tsc.
The .vsix filename follows the pattern operator-terminals-VERSION.vsix.
If code CLI is not on PATH, suggest the user install it via VS Code command palette: "Shell Command: Install 'code' command in PATH".

Changes

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 · 29 lines · 15 tokens per session scan A 8981644d5ea4

Subscribe to this mod's changes

build-vscode-extension is a command published in the GitHub repository untra/operator (37 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 382 once invoked, about $0.0001 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-30.

LLM claude-code gemini-cli kanban tmux

build-vscode-extension

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Build VS Code Extension

Workflow

Notes

What this file has done since we first saw it

Other commands, from other repositories

spec-design

pm-auto-design2dev

card

bug-fix

wtfp:new-paper

setup_research_plan