setup

An interactive setup command for a YAML development environment. YAML is a human-readable format often used for configuration files, and an LSP provides editor support such as validation and language-aware features.

In plain words
What is it for?
Use it to install yaml-language-server, yamllint, Prettier, and yq, verify their versions, and test YAML validation and formatting.
Why use it?
It installs and checks the tools needed to validate, format, and process YAML files, then explains how to enable LSP support. This reduces manual setup work and helps catch configuration errors.

Command

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/zircote/yaml-lsp/setup
Clone the repo
git clone --depth 1 https://github.com/zircote/yaml-lsp
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 287 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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00287
Opus 5 $0.00004 $0.00143
Sonnet 5 $0.00002 $0.00057
Haiku 4.5 $0.00001 $0.00029

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

Security

Grade A, and why

setup 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 2d 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.

commands/setup.md · 78 lines

What it actually says

YAML LSP Setup

This command will configure your YAML development environment with yaml-language-server and essential tools.

Prerequisites Check

First, verify Node.js and Python are installed:

node --version
npm --version
python3 --version

Installation Steps

1. Install yaml-language-server

npm install -g yaml-language-server

2. Install Development Tools

# Validation
pip install yamllint

# Formatting
npm install -g prettier

# YAML processing
brew install yq

3. Verify Installation

yaml-language-server --version
yamllint --version
prettier --version
yq --version

4. Enable LSP in Claude Code

export ENABLE_LSP_TOOL=1

Verification

Test the LSP integration:

# Create a test file
cat > test_lsp.yaml << 'EOF'
name: Test
version: 1.0.0
features:
  - validation
  - formatting
EOF

# Run yamllint
yamllint test_lsp.yaml

# Run prettier
prettier --write test_lsp.yaml

# Clean up
rm test_lsp.yaml
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. 2d ago First seen · 78 lines · 8 tokens per session scan A 5cc7848aa8c2

Subscribe to this mod's changes

setup is a command published in the GitHub repository zircote/yaml-lsp (3 stars, last pushed 22d ago), licensed MIT. It adds 8 tokens to every session and 287 once invoked, about $0.0000 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-31.