Borrowing it
Nothing to install: this file belongs to fengkx/beancount-lsp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fengkx/beancount-lsp/master/.agent/skills/vscode-config/SKILL.mdgit clone --depth 1 https://github.com/fengkx/beancount-lspWrote 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/fengkx/beancount-lsp/vscode-config)<a href="https://agentmods.dev/skills/fengkx/beancount-lsp/vscode-config"><img src="https://agentmods.dev/badge/skills/fengkx/beancount-lsp/vscode-config/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/fengkx/beancount-lsp/vscode-config"><img src="https://agentmods.dev/badge/skills/fengkx/beancount-lsp/vscode-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.01087 |
| Opus 5 | $0.00019 | $0.00544 |
| Sonnet 5 | $0.00008 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
vscode-lsp-configuration 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 8d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VS Code LSP Configuration Skill
Goal
Correctly resolve VS Code settings for an LSP server, including:
- User vs Workspace vs Workspace Folder overrides
- Multi-root workspaces
- Language overrides (
"[lang]") - Cache + invalidation via
onDidChangeConfiguration
Quick SOP (Minimal Correct Implementation)
-
In extension
package.json, set appropriate settingscope:- Prefer
resource(orlanguage-overridable) for most LSP behavior settings.
- Prefer
-
In LSP server, always read settings with
scopeUri = document.uri:- Never rely on
getConfiguration()withoutscopeUriif you expect folder-level settings.
- Never rely on
-
Cache per-resource config:
- Cache key =
document.uri(not workspace root).
- Cache key =
-
Handle config changes:
onDidChangeConfiguration: clear cache and revalidate all open docs.
Configuration Scope (Extension package.json)
What scope controls
contributes.configuration.properties[*].scope declares where a setting is allowed to vary and how VS Code should resolve it.
Common scope values
-
resource- Setting can vary by resource URI (file) and therefore by workspace folder in multi-root.
- Recommended for diagnostics, lint rules, formatter settings, analysis toggles.
-
language-overridable- Allows language-specific overrides like:
"[beancount]": { "yourExtension.enable": true } - Still benefits from reading with
scopeUri.
- Allows language-specific overrides like:
-
window- Window-level only. Does not vary by file/folder.
- Use for UI/window toggles only.
Note:
machine/machine-overridableexist for Remote/machine-specific settings. Most LSPs don’t need them.
Reading Settings in the LSP Server
getConfiguration parameters
Typical Node server call:
connection.workspace.getConfiguration({ scopeUri, section })
-
scopeUri(string URI)- The resource used to resolve configuration (e.g.,
document.uri). - Required for correct behavior in:
- The resource used to resolve configuration (e.g.,
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.
- 8d ago First seen · 162 lines · 39 tokens per session scan A fde5e66571dd
vscode-lsp-configuration is a skill published in the GitHub repository fengkx/beancount-lsp (48 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 1,087 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-09-01.
Other skills, from other repositories
icon-jetbrains
Create or review IntelliJ New UI SVG icons, theme variants, sizes, and palette.
release-jetbrains
Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.
chart
Use when the user asks to visualize data with charts, graphs, or plots using the chart tool (bar, line, scatter, pie, time series, etc.).
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.
lore
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user…
sweetpad
Build, run, and test Xcode and Swift Package apps from the terminal with the sweetpad CLI ("xcodebuild for humans"). Use when the user wants to compile an iOS/macOS/Swift app, run it on a simulator or device, read build errors, run tests, or inspect resolved build settings from the command line — with agent-safe…