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 sgaunet/claude-plugins --skill vscode-settingsgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/sgaunet/claude-plugins/vscode-settings)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/vscode-settings"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/vscode-settings/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/sgaunet/claude-plugins/vscode-settings"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/vscode-settings.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.00048 | $0.02088 |
| Opus 5.5 | $0.00019 | $0.00835 |
| Sonnet 5.5 | $0.00010 | $0.00418 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
vscode-settings 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 22d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VS Code Project Settings
Write a project's .vscode/settings.json from the standard template -- 2-space indentation,
spaces instead of tabs, no symlink following -- plus a per-project title bar and status bar color
so several VS Code windows stay distinguishable at a glance. Settings already in the file are
merged, never clobbered.
When to Use
- A fresh checkout has no
.vscode/settings.jsonyet - Changing a project's window color ("make this one blue")
- Removing the window color again (
none) - The file exists but is missing the indentation or symlink baseline
Color Palette
The background is the chosen color; the foreground is whichever of #15202b or #ffffff contrasts
with it under WCAG. Both are resolved below, so a named color needs no computation.
| Name | Background | Foreground |
|---|---|---|
yellow (default) |
#f9e64f |
#15202b |
blue |
#1f6feb |
#ffffff |
green |
#2ea043 |
#15202b |
red |
#da3633 |
#ffffff |
purple |
#8957e5 |
#ffffff |
orange |
#e36209 |
#15202b |
cyan |
#1f9cb8 |
#15202b |
pink |
#db61a2 |
#15202b |
none (aliases nocolor, no-color) means: write the base settings only and omit
workbench.colorCustomizations entirely.
Workflow
Step 1: Parse Arguments
| Argument | Effect |
|---|---|
--dry-run |
Preview the resulting file, write nothing |
--force |
Skip the final confirmation |
| First bare argument | The color: a palette name, a #rrggbb hex, or none |
A color given as an argument skips Step 3. Anything else is unrecognised -- report it and stop rather than guessing.
Step 2: Locate the Target File
git rev-parse --show-toplevel
Use that path as the project root. If the command fails (not a git repository), use the current
directory. The target is <root>/.vscode/settings.json.
Read the file with the Read tool if it exists, and note whether it contains // comments -- VS
Code accepts JSONC, so a comment is valid content that must survive (Step 6).
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.
- 22d ago First seen · 207 lines · 48 tokens per session scan A bf26b222f9bc
vscode-settings is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 48 tokens to every session and 2,088 once invoked, about $0.0002 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-25.
Other skills, from other repositories
steps
A step-by-step guide writer for tasks such as obtaining API keys, setting up tools, and completing administrative procedures.
onboarding
Use this skill when the user says "set up PM Copilot", "run onboarding", "I'm new here", "help me get started", "initialize my profile", "set up my context", "configure PM Copilot", or when memory/user-profile.md exists but has no content filled in (all fields are still placeholder comments). Also use this skill when…
metrics-dashboard
Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.