setup

An interactive command for setting up a C# development environment with OmniSharp or csharp-ls, tools that provide code understanding for C# projects.

In plain words
What is it for?
Preparing and checking a C# and .NET workspace for language-server use.
Why use it?
It guides developers through checking prerequisites, installing a language server, enabling integration, and verifying the setup with a test project.

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/csharp-lsp/setup
Clone the repo
git clone --depth 1 https://github.com/zircote/csharp-lsp
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 226 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.00009 $0.00226
Opus 5 $0.00005 $0.00113
Sonnet 5 $0.00002 $0.00045
Haiku 4.5 $0.00001 $0.00023

Measured yesterday against content hash 531e8f11ab94, 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 yesterday.

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 TestProject
commands/setup.md · 61 lines

What it actually says

C# LSP Setup

This command will configure your C# development environment with OmniSharp LSP and essential tools.

Prerequisites Check

First, verify .NET is installed:

dotnet --version

Installation Steps

1. Install OmniSharp LSP Server

macOS (Homebrew):

brew install omnisharp

Or using dotnet tool:

dotnet tool install --global csharp-ls

2. Verify Installation

omnisharp --version
# or
csharp-ls --version

3. Enable LSP in Claude Code

export ENABLE_LSP_TOOL=1

Verification

Test the LSP integration:

# Create a test project
dotnet new console -n TestProject && cd TestProject

# Build
dotnet build

# Clean up
cd .. && rm -rf TestProject
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. yesterday First seen · 61 lines · 9 tokens per session scan C 531e8f11ab94

Subscribe to this mod's changes

setup is a command published in the GitHub repository zircote/csharp-lsp (8 stars, last pushed 22d ago), licensed MIT. It adds 9 tokens to every session and 226 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.