Borrowing it
Nothing to install: this file belongs to zircote/terraform-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/zircote/terraform-lsp/main/CLAUDE.mdgit 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/instructions/zircote/terraform-lsp/claude-md)<a href="https://agentmods.dev/instructions/zircote/terraform-lsp/claude-md"><img src="https://agentmods.dev/badge/instructions/zircote/terraform-lsp/claude-md.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.1 | $0.00867 | $0.00867 |
| Opus 5 | $0.00434 | $0.00434 |
| Sonnet 5 | $0.00173 | $0.00173 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
terraform-lsp CLAUDE.md 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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
A Claude Code plugin providing Terraform development support through terraform-ls LSP integration and 17 automated hooks for code quality, security, and infrastructure validation.
Setup
Run /setup to install all required tools, or manually:
# macOS (Homebrew)
brew tap hashicorp/tap
brew install hashicorp/tap/terraform hashicorp/tap/terraform-ls \
tflint trivy checkov terraform-docs infracost terragrunt
Run /validate to verify the plugin installation and tool availability.
Key Files
| File | Purpose |
|---|---|
.lsp.json |
terraform-ls LSP configuration |
hooks/hooks.json |
17 automated development hooks |
.claude/commands/setup.md |
/setup command definition |
.claude/commands/validate.md |
/validate command definition |
.claude-plugin/plugin.json |
Plugin metadata |
Hook System
All hooks trigger on PostToolUse after Write|Edit operations. Hooks use command -v checks to skip gracefully when optional tools aren't installed.
Hook categories:
- Core (
.tf): format, validate, init check, plan hint - Linting (
.tf): tflint, todo/fixme detection - Security (
.tf): trivy, checkov, sensitive value detection - Variables (
.tfvars): format, sensitive check - Terragrunt (
terragrunt.hcl): format, validate - Hints (
main.tf,variables.tf): docs, cost, provider upgrade suggestions
When Modifying Hooks
Edit hooks/hooks.json. The hooks use Claude Code's standard event-based format:
{
"hooks": {
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [{ "type": "command", "command": "..." }],
"conditions": { "fileExtensions": [".tf"] }
}
]
}
}
Key fields:
matcher: Tool name pattern (e.g.,Write|Editfor file operations)conditions.fileExtensions: File types to match (e.g.,[".tf", ".tfvars"])conditions.pathPatterns: Path globs for specific files (e.g.,["**/main.tf"])
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.
- 7d ago First seen · 99 lines · 867 tokens per session scan A e5c4c98003ab
terraform-lsp CLAUDE.md is an instructions file published in the GitHub repository zircote/terraform-lsp (2 stars, last pushed 28d ago), licensed MIT. It adds 867 tokens to every session, about $0.0043 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.