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/analysis-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.00029 | $0.00319 |
| Opus 5 | $0.00015 | $0.00160 |
| Sonnet 5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
analysis-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 analysis/.
What this is and is NOT
The only place in the repo where both vocabularies may meet. LSP concepts stop here going down; graph concepts stop here coming up. A "symbol" becomes a node with a type tag you define; "calls" becomes a typed edge.
You do not add anything to graph-lite/. If a translation feels like it belongs
in the library, it does not — invert it, or pass the data in.
Hard rules
- No LSP type crosses into a graph-lite call. Translate at the seam; never pass a struct through and let the library read one field.
- Node id mapping is a one-way door. Ids persist. The scheme must survive a rename and a function moving forty lines. Decide it in an ADR, not inline.
- Deleting a node must not orphan an edge. A dangling edge is a corrupt answer, not a missing one.
- Files ≤ 500 lines. Custom errors. RAII.
Read first
docs/analysis/README.md · docs/architecture/graph-lite-boundary.md ·
docs/architecture/tiers.md.
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 · 36 lines · 29 tokens per session scan A 2e3e71552066
analysis-dev is an agent published in the GitHub repository developerz-ai/universal-lsp (0 stars, last pushed 9d ago), licensed Apache-2.0. It adds 29 tokens to every session and 319 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
compiler-config
Use this agent for tasks involving compiler configuration in .properties files - adding, removing, modifying, or aliasing compilers. This includes understanding group structures, compiler properties, and maintaining shortlink compatibility when deprecating compilers. USE PROACTIVELY when the user mentions a PR adding…
frontend-developer
Use this agent for frontend planning, reviews, and refactors in this repository. Focus on the frontend source tree, shared UI, i18n boundaries, and the build/runtime constraints documented in AGENTS.md and LAWS.md.
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.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.