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.
/plugin marketplace add zircote/yaml-lspnpx agentmods add plugins/zircote/yaml-lsp/yaml-lspgit clone --depth 1 https://github.com/zircote/yaml-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/plugins/zircote/yaml-lsp/yaml-lsp)<a href="https://agentmods.dev/plugins/zircote/yaml-lsp/yaml-lsp"><img src="https://agentmods.dev/badge/plugins/zircote/yaml-lsp/yaml-lsp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
yaml-lsp 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.
What it actually says
{
"name": "yaml-lsp",
"version": "0.1.2",
"description": "YAML language server plugin for Claude Code with yaml-language-server integration and automated hooks for validation and formatting",
"author": {
"name": "zircote",
"email": "[email protected]"
},
"repository": "https://github.com/zircote/yaml-lsp",
"license": "MIT",
"keywords": [
"yaml",
"yml",
"lsp",
"language-server",
"claude-plugin",
"code-assistant",
"yamllint",
"prettier"
]
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 8 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 22 lines scan A 0278cc748697
yaml-lsp is a plugin published in the GitHub repository zircote/yaml-lsp (3 stars, last pushed 24d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
Other plugins, from other repositories
csharp-lsp
Claude Code plugin for C# development with OmniSharp LSP integration, 12 automated hooks for .NET builds, linting, formatting, and testing (xUnit, NUnit).
cpp-lsp
Claude Code plugin for C/C++ development with clangd LSP integration, 14 automated hooks for compilation, linting (clang-tidy), formatting (clang-format), and memory analysis (valgrind).
svelte-lsp
Svelte language server plugin for Claude Code with svelte-language-server integration and automated hooks for linting and formatting.
go-lsp
Claude Code plugin for Go development with gopls LSP integration, 14 automated hooks for linting (golangci-lint), formatting (gofmt), testing, and security scanning (govulncheck).
python-lsp
Claude Code plugin for Python development with Pyright LSP integration, 15 automated hooks for type checking, linting (ruff), formatting (black), testing (pytest), and security scanning.
scala-lsp
Scala language server plugin for Claude Code with Metals LSP integration and automated hooks for formatting, linting, and testing.