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 agents/developerz-ai/universal-lsp/docs-devgit clone --depth 1 https://github.com/developerz-ai/universal-lspWhat 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.00022 | $0.00345 |
| Opus 5 | $0.00011 | $0.00172 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
docs-dev 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 today.
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
You own docs/ and README.md.
Rules
- Lead with the rule, not the reason. Fragments over sentences. Tables over paragraphs. Paths and commands verbatim.
- Reference, never paste.
path:line. Copied code is stale on arrival. - Date load-bearing claims (
As of 2026-08). Delete beats update when in doubt — a wrong doc costs more than a missing one. - Gap statements rot fastest. Never "we haven't done X yet"; write "when you do
X, follow
path". - Preventive rules →
CLAUDE.md(read every session). Symptom lookups →docs/gotchas.md(read when something breaks). Keeping that split is what stopsCLAUDE.mdbecoming a runbook. docs/graph-lite/is written as though the library already stands alone and is scanned by a lint guard. Anything needing both vocabularies at once goes indocs/architecture/.- A universal claim about a named symbol ("always", "never", "every") needs the enumeration that makes it true, in the same change.
Verify
bun run scripts/lint/index.ts — doc-links fails on a dead relative link.
Shared checkout
Scope commands to your files. Concurrency 1. No git operations, never git stash.
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.
- today First seen · 34 lines · 22 tokens per session scan A b75490fef027
docs-dev is an agent published in the GitHub repository developerz-ai/universal-lsp (0 stars, last pushed 10d ago), licensed Apache-2.0. It adds 22 tokens to every session and 345 once invoked, about $0.0001 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 agents, from other repositories
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
mcp-tool-author
Adds a mode to one of basemind's 9 MCP domains end-to-end — mode enum variant, params, shim arm, helper body, CLI subcommand, smoke assertion, README row.
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…
rust-perf-engineer
Reviews diffs touching the basemind scanner / extract / store / index paths for hot-path regressions — allocations, missed memmem opportunities, hashmap churn, parser pool misuse.