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/go-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/go-lsp/setup)<a href="https://agentmods.dev/commands/zircote/go-lsp/setup"><img src="https://agentmods.dev/badge/commands/zircote/go-lsp/setup/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/commands/zircote/go-lsp/setup"><img src="https://agentmods.dev/badge/commands/zircote/go-lsp/setup.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.00404 |
| Opus 5.5 | $0.00003 | $0.00162 |
| Sonnet 5.5 | $0.00002 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade C, and why
setup scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
cd - && rm -rf /tmp/test-go-lsp What it actually says
Go LSP Setup
This command will configure your Go development environment with gopls LSP and essential tools.
Prerequisites Check
First, verify Go is installed:
go version
Ensure ~/go/bin is in your PATH:
echo 'export PATH=$PATH:$(go env GOPATH)/bin' >> ~/.zshrc
source ~/.zshrc
Installation Steps
1. Install gopls LSP Server
go install golang.org/x/tools/gopls@latest
2. Install Development Tools
# Linting
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
# Security scanning
go install golang.org/x/vuln/cmd/govulncheck@latest
go install github.com/securego/gosec/v2/cmd/gosec@latest
# Import management
go install golang.org/x/tools/cmd/goimports@latest
# Static analysis
go install honnef.co/go/tools/cmd/staticcheck@latest
3. Verify Installation
gopls version
golangci-lint --version
govulncheck -version
4. Enable LSP in Claude Code
export ENABLE_LSP_TOOL=1
Verification
Test the LSP integration:
# Create a test module
mkdir -p /tmp/test-go-lsp && cd /tmp/test-go-lsp
go mod init test
echo 'package main; func main() { println("Hello") }' > main.go
# Run checks
go vet ./...
golangci-lint run
# Clean up
cd - && rm -rf /tmp/test-go-lsp
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 · 80 lines · 8 tokens per session scan C d42d23adc7d9
setup is a command published in the GitHub repository zircote/go-lsp (4 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 404 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
setup
Interactive setup for C/C++ LSP development environment.
setup
Interactive setup for Python LSP development environment.
setup
Interactive setup for Kotlin LSP development environment.
setup
Interactive setup for Lua LSP development environment.
setup
Interactive setup for C# LSP development environment.
setup
Interactive setup for Java LSP development environment.