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 agentmods add skills/microsoft/vscode-copilot-chat/project-setup-info-localnpx skills add microsoft/vscode-copilot-chat --skill project-setup-info-localgit clone --depth 1 https://github.com/microsoft/vscode-copilot-chatWrote 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-copilot-chat/project-setup-info-local)<a href="https://agentmods.dev/skills/microsoft/vscode-copilot-chat/project-setup-info-local"><img src="https://agentmods.dev/badge/skills/microsoft/vscode-copilot-chat/project-setup-info-local.svg" alt="Measured on agentmods" 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 | $0.00263 | $0.01700 |
| Opus 5 | $0.00131 | $0.00850 |
| Sonnet 5 | $0.00053 | $0.00340 |
| Haiku 4.5 | $0.00026 | $0.00170 |
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 4d 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.
This is a copy
100% identical to project-setup-info-local — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 tots-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 tonpm.--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
- Do not remove any arguments from the command. Only add arguments if the user requests them.
- Call the tool
get_vscode_apiwith the user's query to get the relevant references. - After the tool
get_vscode_apihas 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.
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.
- 4d ago First seen · 128 lines · 263 tokens per session scan A 6205fdc9201e
project-setup-info-local is a skill published in the GitHub repository microsoft/vscode-copilot-chat (9,971 stars, last pushed 3mo ago), licensed MIT. It adds 263 tokens to every session and 1,700 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to project-setup-info-local, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…