Borrowing it
Nothing to install: this file belongs to blackwell-systems/agent-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/blackwell-systems/agent-lsp/main/CLAUDE.mdgit clone --depth 1 https://github.com/blackwell-systems/agent-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/blackwell-systems/agent-lsp/claude-md)<a href="https://agentmods.dev/instructions/blackwell-systems/agent-lsp/claude-md"><img src="https://agentmods.dev/badge/instructions/blackwell-systems/agent-lsp/claude-md.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.01077 | $0.01077 |
| Opus 5 | $0.00539 | $0.00539 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
agent-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 7d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-lsp Skills
agent-lsp provides 66 code intelligence tools and 23 workflow skills. Prefer these tools over text search for code intelligence tasks.
Before editing code: call blast_radius for blast-radius analysis.
Before applying edits: call preview_edit to preview the diagnostic delta.
After any change: call get_diagnostics, then run_build and run_tests.
Task-to-tool mapping (use these instead of Read/Grep for code):
| Task | Use this | Not this |
|---|---|---|
| See file structure | list_symbols |
Read + manual scanning |
| Find a symbol by name | find_symbol |
Grep across files |
| Find all usages | find_references |
Grep for the name |
| Understand a symbol | inspect_symbol |
Read the file |
| What calls this function | find_callers |
Grep for the name |
| Replace a function body | replace_symbol_body |
Edit with text matching |
| Delete unused symbol | safe_delete_symbol |
Edit to remove lines |
| Skill | Description |
|---|---|
/lsp-architecture |
Generate a structural architecture overview of a codebase: languages, package map, entry points, dependency graph, an... |
/lsp-concurrency-audit |
Concurrency safety audit for a type or file. Maps all fields, traces which are accessed from concurrent contexts (gor... |
/lsp-cross-repo |
Cross-repository analysis — find all callers of a library symbol in one or more consumer repos. Use when refactorin... |
/lsp-dead-code |
Enumerate exported symbols in a file and surface those with zero references across the workspace. Use when auditing f... |
/lsp-docs |
Three-tier documentation lookup for any symbol — hover → offline toolchain doc → source definition. Use when ho... |
/lsp-edit-export |
Safe workflow for editing exported symbols or public APIs. Use when changing a function signature, modifying a public... |
/lsp-edit-symbol |
Edit a named symbol without knowing its file or position. Use when you want to change a function, type, or variable b... |
/lsp-explore |
Tell me about this symbol": hover + implementations + call hierarchy + references in one pass — for navigating unfa... |
/lsp-extract-function |
Extract a selected code block into a named function. Primary path uses the language server's extract-function code ac... |
/lsp-fix-all |
Apply available quick-fix code actions for all current diagnostics in a file, one at a time with re-collection betwee... |
/lsp-format-code |
Format a file or selection using the language server's formatter. Use before committing to apply consistent style, or... |
/lsp-generate |
Trigger language server code generation — implement interface stubs, generate test skeletons, add missing methods, ... |
/lsp-impact |
Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count befor... |
/lsp-implement |
Find all concrete implementations of an interface or abstract type. Use when you need to know what types satisfy an i... |
/lsp-inspect |
Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), c... |
/lsp-local-symbols |
Fast file-scoped symbol analysis — find all usages of a symbol within the current file, list all symbols defined in... |
/lsp-onboard |
First-session project onboarding. Explores the project structure, detects build system, test runner, entry points, an... |
/lsp-refactor |
End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run af... |
/lsp-rename |
Two-phase safe rename across the entire workspace. Use when renaming any symbol, function, method, variable, type, or... |
/lsp-safe-edit |
Wrap any code edit with before/after diagnostic comparison. Speculatively previews the change first (preview_edit), t... |
/lsp-simulate |
Speculative code editing session — simulate changes in memory before touching disk. Use when planning edits that mi... |
/lsp-test-correlation |
Find and run the tests that cover a source file. Use after editing a file to discover exactly which test files and te... |
/lsp-understand |
Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, im... |
/lsp-verify |
Full three-layer verification after any change — LSP diagnostics + compiler build + test suite, ranked by severity.... |
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.
- 7d ago First seen · 52 lines · 1,077 tokens per session scan A c45415c827e6
agent-lsp CLAUDE.md is an instructions file published in the GitHub repository blackwell-systems/agent-lsp (121 stars, last pushed yesterday), licensed MIT. It adds 1,077 tokens to every session, about $0.0054 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.