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/elixir-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/elixir-lsp/setup)<a href="https://agentmods.dev/commands/zircote/elixir-lsp/setup"><img src="https://agentmods.dev/badge/commands/zircote/elixir-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/elixir-lsp/setup"><img src="https://agentmods.dev/badge/commands/zircote/elixir-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.00009 | $0.00292 |
| Opus 5.5 | $0.00004 | $0.00117 |
| Sonnet 5.5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
setup 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
Elixir LSP Setup
This command will configure your Elixir development environment with ElixirLS and essential tools.
Prerequisites Check
First, verify Elixir is installed:
elixir --version
mix --version
Installation Steps
1. Install ElixirLS
Download from GitHub releases: https://github.com/elixir-lsp/elixir-ls/releases
Or build from source:
git clone https://github.com/elixir-lsp/elixir-ls.git
cd elixir-ls
mix deps.get && mix compile
mix elixir_ls.release -o release
2. Install Development Tools
# Update hex and rebar
mix local.hex --force
mix local.rebar --force
# Install Credo for linting
mix archive.install hex credo --force
3. Enable LSP in Claude Code
export ENABLE_LSP_TOOL=1
Verification
Test the integration:
# Create a test file
cat > test_lsp.ex << 'EOF'
defmodule Greeter do
def greet(name), do: "Hello, #{name}!"
end
EOF
# Format
mix format test_lsp.ex
# Clean up
rm test_lsp.ex
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 · 69 lines · 9 tokens per session scan A 36c891cdd830
setup is a command published in the GitHub repository zircote/elixir-lsp (1 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 292 once invoked, about $0.0000 per session on Opus 5.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 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 YAML LSP development environment.
setup
Interactive setup for Scala LSP development environment.
setup
Interactive setup for JSON LSP development environment.
setup
Interactive setup for Bash LSP development environment.