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/scala-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/scala-lsp/setup)<a href="https://agentmods.dev/commands/zircote/scala-lsp/setup"><img src="https://agentmods.dev/badge/commands/zircote/scala-lsp/setup.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.00008 | $0.00269 |
| Opus 5 | $0.00004 | $0.00134 |
| Sonnet 5 | $0.00002 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
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 6d 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
Scala LSP Setup
This command will configure your Scala development environment with Metals and essential tools.
Prerequisites Check
First, verify Coursier is installed:
cs --version
If not installed:
brew install coursier/formulas/coursier
Installation Steps
1. Install Metals LSP Server
cs install metals
2. Install Development Tools
# Formatting
cs install scalafmt
# Linting and refactoring
cs install scalafix
3. Verify Installation
metals --version
scalafmt --version
4. Enable LSP in Claude Code
export ENABLE_LSP_TOOL=1
Verification
Test the LSP integration:
# Create a test file
cat > test_lsp.scala << 'EOF'
object Main extends App {
def greet(name: String): String = s"Hello, $name!"
println(greet("World"))
}
EOF
# Run Scalafmt
scalafmt test_lsp.scala
# Clean up
rm test_lsp.scala
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.
- 6d ago First seen · 73 lines · 8 tokens per session scan A f2ef89054958
setup is a command published in the GitHub repository zircote/scala-lsp (3 stars, last pushed 27d ago), licensed MIT. It adds 8 tokens to every session and 269 once invoked, about $0.0000 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 commands, from other repositories
setup
Interactive setup for Kotlin LSP development environment.
setup
Interactive setup for Java LSP development environment.
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 Bash LSP development environment.