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.
git 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/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/plugins/zircote/yaml-lsp/yaml-lsp"><img src="https://agentmods.dev/badge/plugins/zircote/yaml-lsp/yaml-lsp.svg" alt="Reviewed on agentmods" width="80" 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 1mo 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.
- 1mo 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 2mo 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
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).
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
logic-lens
Logic-first code review using semi-formal execution tracing. Surfaces behavioral bugs, type contract breaches, boundary blindspots, and interprocedural semantic mismatches — the logic errors that cause production incidents in syntax-clean code.
powershell-lsp
Real PowerShell analysis after every AI edit -- with proof it ran. Hover, go-to-definition, and find-references serve natively through an opt-in handshake shim (userConfig nativeServe, off by default).
logic-lens
Logic-first code review using semi-formal execution tracing. Surfaces behavioral bugs, semantic errors, and runtime failures that linters miss.
craftsman
Ship something with Lovable, Replit, Bolt, v0, Claude Code, or Codex and it works, but nobody with an engineering background has checked it. This is the engineering review you'd get from the technical co-founder you don't have. craft-audit checks the whole project across ten areas: UX, frontend, backend, database…