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.
npx agentmods add instructions/asyncswap/solidity-language-server/agents-mdgit clone --depth 1 https://github.com/asyncswap/solidity-language-serverWhat 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 | $0.03184 | $0.03184 |
| Opus 5 | $0.01592 | $0.01592 |
| Sonnet 5 | $0.00637 | $0.00637 |
| Haiku 4.5 | $0.00318 | $0.00318 |
Grade A, and why
solidity-language-server AGENTS.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 2d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents
- Use
jqto analyze json outputs from ast. - poolmanager.json - ast generated by solc (single-file build fixture for PoolManager).
Prerequisites: AST Identity Model
Before working on any feature that touches goto-definition, references, call hierarchy, implementation, rename, or the caching system, you must understand how file IDs and node IDs work. Getting this wrong causes cross-build collisions that are extremely hard to debug (a function in one build silently maps to a completely different function in another build).
The two ID types
| Type | Defined in | Inner | Assigned by | Stable across compilations? |
|---|---|---|---|---|
FileId(u64) |
types.rs:24 |
unsigned 64-bit | PathInterner (canonical) |
Yes — same path always gets same ID |
NodeId(i64) |
types.rs:4 |
signed 64-bit | solc (per-compilation) | No — same function can get different IDs |
There is also SolcFileId(String) — a string wrapper used as HashMap keys matching
solc's JSON output (e.g. "0", "34"). It is the stringified form of a file ID.
Node IDs are signed because solc uses negative IDs for built-in symbols (-1 for
abi, -15 for msg, -18 for require, -28 for this).
The src string format
Every AST node has a src field in the format "offset:length:fileId":
offset— byte offset from the start of the source filelength— byte length of the source rangefileId— which source file this location belongs to
Parsed by SourceLoc::parse() in types.rs. After canonicalization, fileId is a
canonical FileId from the PathInterner, not solc's original per-compilation ID.
Why file IDs are unstable from solc
Solc assigns file IDs sequentially based on input order. If you compile Foo.sol first,
it gets ID 0. If you compile Bar.sol first, Foo.sol gets a different ID. A single-file
build of PoolManager.sol produces different file IDs than a full project build that
includes all 160 source files.
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.
- 2d ago First seen · 287 lines · 3,184 tokens per session scan A 026773c2bc46
solidity-language-server AGENTS.md is an instructions file published in the GitHub repository asyncswap/solidity-language-server (21 stars, last pushed 1mo ago), licensed MIT. It adds 3,184 tokens to every session, about $0.0159 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
prb-math AGENTS.md
Instructions for PaulRBerg/prb-math, covering prbmath, stack, structure, commands and development.
evmole AGENTS.md
Instructions for cdump/evmole: EVMole extracts structured facts from deployed EVM runtime bytecode.
mcp-tenderly CLAUDE.md
Claude Code instructions for py-zoid/mcp-tenderly, covering mcp-tenderly, commands, layout, constraints worth knowing before you change anything and testing against real tenderly.
prb-math CLAUDE.md
Instructions for PaulRBerg/prb-math, a project described as: Solidity library for advanced fixed-point math.
tevm CLAUDE.md
Claude Code instructions for evmts/tevm, covering tevm monorepo commands and style guide, project overview, forking implementation, json-rpc support and commands.
agent-lsp CLAUDE.md
Instructions for blackwell-systems/agent-lsp, a project described as: MCP server that orchestrates language servers into agent-native workflows. 65 tools, 30 CI-verified languages.