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 agentmods add commands/zircote/terraform-lsp/validategit clone --depth 1 https://github.com/zircote/terraform-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/commands/zircote/terraform-lsp/validate)<a href="https://agentmods.dev/commands/zircote/terraform-lsp/validate"><img src="https://agentmods.dev/badge/commands/zircote/terraform-lsp/validate.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01753 |
| Opus 5 | $0.00000 | $0.00877 |
| Sonnet 5 | $0.00000 | $0.00351 |
| Haiku 4.5 | $0.00000 | $0.00175 |
Grade A, and why
validate 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 3d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Terraform LSP Plugin
Comprehensive validation of the terraform-lsp plugin including structure, tools, LSP, and hooks.
Instructions
Execute each validation step and report results using checkmarks for pass, X for fail.
1. Plugin Structure Validation
Check required files exist:
echo "=== Plugin Structure Validation ===" && [ -f "$CLAUDE_PROJECT_DIR/.lsp.json" ] && echo "[PASS] .lsp.json" || echo "[FAIL] .lsp.json"
[ -f "$CLAUDE_PROJECT_DIR/.claude-plugin/plugin.json" ] && echo "[PASS] plugin.json" || echo "[FAIL] plugin.json"
[ -f "$CLAUDE_PROJECT_DIR/hooks/hooks.json" ] && echo "[PASS] hooks.json" || echo "[FAIL] hooks.json"
[ -f "$CLAUDE_PROJECT_DIR/commands/setup.md" ] && echo "[PASS] setup.md" || echo "[FAIL] setup.md"
[ -f "$CLAUDE_PROJECT_DIR/README.md" ] && echo "[PASS] README.md" || echo "[FAIL] README.md"
[ -f "$CLAUDE_PROJECT_DIR/CLAUDE.md" ] && echo "[PASS] CLAUDE.md" || echo "[FAIL] CLAUDE.md"
[ -d "$CLAUDE_PROJECT_DIR/tests" ] && [ -f "$CLAUDE_PROJECT_DIR/tests/main.tf" ] && echo "[PASS] tests/ directory" || echo "[FAIL] tests/ directory"
2. Configuration Validation
Validate JSON files are parseable:
echo "=== Configuration Validation ===" && python3 -m json.tool "$CLAUDE_PROJECT_DIR/.lsp.json" > /dev/null 2>&1 && echo "[PASS] .lsp.json valid JSON" || echo "[FAIL] .lsp.json invalid"
python3 -m json.tool "$CLAUDE_PROJECT_DIR/.claude-plugin/plugin.json" > /dev/null 2>&1 && echo "[PASS] plugin.json valid JSON" || echo "[FAIL] plugin.json invalid"
python3 -m json.tool "$CLAUDE_PROJECT_DIR/hooks/hooks.json" > /dev/null 2>&1 && echo "[PASS] hooks.json valid JSON" || echo "[FAIL] hooks.json invalid"
grep -q '"terraform"' "$CLAUDE_PROJECT_DIR/.lsp.json" && echo "[PASS] LSP has terraform entry" || echo "[FAIL] LSP missing terraform entry"
echo "[INFO] Hook count:" && grep -c '"name":' "$CLAUDE_PROJECT_DIR/hooks/hooks.json"
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.
- 3d ago First seen · 220 lines · 0 tokens per session scan A fd2f83795851
validate is a command published in the GitHub repository zircote/terraform-lsp (2 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,753 tokens. 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 commands, from other repositories
seo-drift
Compare two SEO snapshots (GSC / GSC AI Performance / rank tracker / AEO probe) and surface top movers per metric with auto-classification — growth / decline / reshuffle / stable / new / lost.
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
save
Save this conversation as a new or existing reusable context.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
index
Command "index" from MadaraUchiha-314/the-loop, covering commands, the control plane, daemon commands, repo-scoped commands and maintenance.