project-setup-info-local

project-setup-info-local is a skill for Claude Code, Codex from microsoft/vscode. It costs 263 tokens per session (1,700 once invoked), scanned A, original, MIT.

A guide for setting up a complete project structure in a VS Code workspace, including starter templates for project types such as VS Code extensions. It is intended for initializing whole projects rather than individual files.

In plain words
What is it for?
Use it when creating a complete project from scratch, such as a VS Code extension, and choosing its language, package manager, or build setup.
Why use it?
It gives a new project a consistent starting structure and the commands needed to scaffold it.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit Use it when creating a complete project from scratch, such as a VS Code extension, and choosing its language, package manager, or build setup.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/vscode/project-setup-info-local
About the project

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.

microsoft/vscode · 193,981 stars · on GitHub · code.visualstudio.com

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.

Any agent
npx skills add microsoft/vscode --skill project-setup-info-local
Clone the repo
git clone --depth 1 https://github.com/microsoft/vscode

Made for: Claude Code, Codex.

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.

agentmods badge for project-setup-info-local

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/vscode/project-setup-info-local/github.svg)](https://agentmods.dev/skills/microsoft/vscode/project-setup-info-local)
Your own site
<a href="https://agentmods.dev/skills/microsoft/vscode/project-setup-info-local"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/project-setup-info-local/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.

agentmods 80×15 button for project-setup-info-local

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/vscode/project-setup-info-local"><img src="https://agentmods.dev/badge/skills/microsoft/vscode/project-setup-info-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 263 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,700 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk pass 6 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 17
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 44
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 70
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00263 $0.01700
Opus 5.5 $0.00105 $0.00680
Sonnet 5.5 $0.00053 $0.00340
Haiku 4.5 $0.00026 $0.00170

Measured 1mo ago against content hash 6205fdc9201e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

project-setup-info-local 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

extensions/copilot/assets/prompts/skills/project-setup-info-local/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

How to setup a project

Determine what kind of project the user wants to create, then based on that, choose which setup info below to follow. Only setup a project if the folder is empty or if you've just called the tool first calling the tool to create a workspace.

vscode-extension

A template for creating a VS Code extension using Yeoman and Generator-Code.

Run this command:

npx --package yo --package generator-code -- yo code . --skipOpen

The command has the following arguments:

  • -t, --extensionType: Specify extension type: ts, js, command-ts, command-js, colortheme, language, snippets, keymap, extensionpack, localization, commandweb, notebook. Defaults to ts
  • -n, --extensionDisplayName: Set the display name of the extension.
  • --extensionId: Set the unique ID of the extension. Do not select this option if the user has not requested a unique ID.
  • --extensionDescription: Provide a description for the extension.
  • --pkgManager: Specify package manager: npm, yarn, or pnpm. Defaults to npm.
  • --bundler: Bundle the extension using webpack or esbuild.
  • --gitInit: Initialize a Git repository for the extension.
  • --snippetFolder: Specify the location of the snippet folder.
  • --snippetLanguage: Set the language for snippets.

Rules

  1. Do not remove any arguments from the command. Only add arguments if the user requests them.
  2. Call the tool get_vscode_api with the user's query to get the relevant references.
  3. After the tool get_vscode_api has completed, only then begin to modify the project.

next-js

A React based framework for building server-rendered web applications.

Run this command:

npx create-next-app@latest .

The command has the following arguments:

  • --ts, --typescript: Initialize as a TypeScript project. This is the default.
  • --js, --javascript: Initialize as a JavaScript project.
  • --tailwind: Initialize with Tailwind CSS config. This is the default.
  • --eslint: Initialize with ESLint config.
  • --app: Initialize as an App Router project.
  • --src-dir: Initialize inside a 'src/' directory.
  • --turbopack: Enable Turbopack by default for development.
  • --import-alias <prefix/*>: Specify import alias to use.(default is "@/*")
  • --api: Initialize a headless API using the App Router.
  • --empty: Initialize an empty project.
  • --use-npm: Explicitly tell the CLI to bootstrap the application using npm.
  • --use-pnpm: Explicitly tell the CLI to bootstrap the application using pnpm.
  • --use-yarn: Explicitly tell the CLI to bootstrap the application using Yarn.
  • --use-bun: Explicitly tell the CLI to bootstrap the application using Bun.

Read the full file on GitHub · 128 lines

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.

  1. 1mo ago First seen · 128 lines · 263 tokens per session scan A 6205fdc9201e

Subscribe to this mod's changes

project-setup-info-local is a skill published in the GitHub repository microsoft/vscode (193,981 stars, last pushed today), licensed MIT. It adds 263 tokens to every session and 1,700 once invoked, about $0.0011 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-03.

Related

Other skills, from other repositories

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…

prisma/orm · 220 tokens

resolution_playbook

How to choose one resolution action from a ticket and its customer history.

open-mercato/open-mercato · 14 tokens

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…

PostHog/posthog · 136 tokens

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.

Playa-0v0/Cyrene-Agent · 42 tokens

cyrene-diagram

A design guide for making static SVG learning cards: small diagrams or reference cards rendered as images. It explains when to use a card instead of Mermaid, a text-based diagram format, and sets layout, color, size, and safety rules.

Playa-0v0/Cyrene-Agent · 50 tokens

instar-project

Register, inspect, and drive multi-spec projects via the instar /projects API. Twelve subcommands cover the full Phase 1 surface — create / status / next / advance / drift / run-round / halt / ack / resume / abandon / accept-partial / claim-ownership.

JKHeadley/instar · 61 tokens