setup

An interactive setup command for Go development with gopls, a Go language server that provides code intelligence. It also installs tools for linting, security checks, imports, and static analysis.

In plain words
What is it for?
Use it to install and check Go development tools, enable language-server support in Claude Code, and run basic checks on a test Go module.
Why use it?
It gathers the environment setup and verification steps in one guided process, reducing manual configuration work.

Command

Install

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.

agentmods
npx agentmods add commands/zircote/go-lsp/setup
Clone the repo
git clone --depth 1 https://github.com/zircote/go-lsp
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 404 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00404
Opus 5 $0.00004 $0.00202
Sonnet 5 $0.00002 $0.00081
Haiku 4.5 $0.00001 $0.00040

Measured 2d ago against content hash d42d23adc7d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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
commands/setup.md · 80 lines

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
Changes

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.

  1. 2d ago First seen · 80 lines · 8 tokens per session scan C d42d23adc7d9

Subscribe to this mod's changes

setup is a command published in the GitHub repository zircote/go-lsp (3 stars, last pushed 23d ago), licensed MIT. It adds 8 tokens to every session and 404 once invoked, about $0.0000 per session on Opus 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.