Borrowing it
Nothing to install: this file belongs to developerz-ai/universal-lsp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/developerz-ai/universal-lsp/main/CLAUDE.mdgit clone --depth 1 https://github.com/developerz-ai/universal-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/instructions/developerz-ai/universal-lsp/claude-md)<a href="https://agentmods.dev/instructions/developerz-ai/universal-lsp/claude-md"><img src="https://agentmods.dev/badge/instructions/developerz-ai/universal-lsp/claude-md/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/instructions/developerz-ai/universal-lsp/claude-md"><img src="https://agentmods.dev/badge/instructions/developerz-ai/universal-lsp/claude-md.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.03483 | $0.03483 |
| Opus 5.5 | $0.01393 | $0.01393 |
| Sonnet 5.5 | $0.00697 | $0.00697 |
| Haiku 4.5 | $0.00348 | $0.00348 |
Grade A, and why
universal-lsp CLAUDE.md 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Universal LSP + graph-lite
One C++ language server for many languages (Lua-declared plugins, no external language-server processes), plus graph-lite — the embeddable graph library it runs on. Built for a terminal-first, agent-driven world; standard LSP for editors, MCP for agents.
Status: pre-implementation. Repo infrastructure, gates and docs are in place;
build phase 1 (graph-lite core) is the current work. Scope: docs/spec.md.
This repo is AI-first. Agents write the code; humans review at the PR. Every rule below exists to make that loop fast and safe.
Response rules
- Execute. No preamble, no "I'll start by…", no restating the task.
- Lead with action or answer. Reasoning after, only if non-obvious.
- Batch independent tool calls. Read several files at once, grep in parallel.
- Never speculate about code you have not read. Read first.
- Disagree when the user is wrong. State the correction, once.
- Terse. Fragments fine. Commands, paths and code stay exact.
- End summary: 1–2 sentences.
Coding rules
- Fail fast, loudly. A crash on a bad assumption beats a wrong answer. Invalid config throws; it never silently degrades. Validate at the seam where the bad value enters, not three layers down.
- Optimize for the next debugger. Errors name the value, the seam, and the fix. One seam per invariant — one place to look, one place to fix.
- Simplicity. Minimum code that solves the stated problem. No speculative abstraction, no config knob nobody asked for, no error handling for impossible cases. Concrete first; introduce an interface when the SECOND implementation actually arrives.
- Surgical. Every changed line traces to the request. No drive-by reformatting. Match surrounding style.
- Verifiable done. Convert the task to a command that proves it. Bug → reproducing test first. Refactor → green before AND after.
- TDD is the working method here, not an aspiration. Write the failing test, then the code. This project has no UI to eyeball and no staging to poke: a test is the only thing that says "done".
- Ship the guard with the fix. A defect that can recur gets its mechanical
guard — a test, an assertion at the seam, a
scripts/lint/rule — in the SAME PR. Prose telling the next agent to be careful is a bug report against tooling. - Never ship a fix you know is wrong. Say so in one sentence and take the right
path. Never silence a failing test, a warning, or a guard to get green — the
guard is the asset. If the quick fix is chosen anyway, pin the known-bad
behaviour with a test; never a bare
TODO, nobody greps those. - One path, replaced completely. No shims, no dual paths, no feature flags,
no
v2besidev1. Public contracts (the LSP surface, MCP tool names, the graph-lite header, the persistence format) are the genuine exception — those are one-way doors; name them and think before shipping.
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.
- 2mo ago First seen · 231 lines · 3,483 tokens per session scan A 0195d50784c9
universal-lsp CLAUDE.md is an instructions file published in the GitHub repository developerz-ai/universal-lsp (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 3,483 tokens to every session, about $0.0139 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 instructions, from other repositories
weld cpp.instructions.md
C++ naming and structure guidance.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).