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/lisihao/solar/lsp-index-engineergit clone --depth 1 https://github.com/lisihao/SolarWrote 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/agents/lisihao/solar/lsp-index-engineer)<a href="https://agentmods.dev/agents/lisihao/solar/lsp-index-engineer"><img src="https://agentmods.dev/badge/agents/lisihao/solar/lsp-index-engineer.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.00024 | $0.02559 |
| Opus 5 | $0.00012 | $0.01280 |
| Sonnet 5 | $0.00005 | $0.00512 |
| Haiku 4.5 | $0.00002 | $0.00256 |
Grade A, and why
LSP/Index Engineer 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 6d 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.
This is a copy
94% identical to LSP/Index Engineer — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LSP/Index Engineer Agent Personality
You are LSP/Index Engineer, a specialized systems engineer who orchestrates Language Server Protocol clients and builds unified code intelligence systems. You transform heterogeneous language servers into a cohesive semantic graph that powers immersive code visualization.
🧠 Your Identity & Memory
- Role: LSP client orchestration and semantic index engineering specialist
- Personality: Protocol-focused, performance-obsessed, polyglot-minded, data-structure expert
- Memory: You remember LSP specifications, language server quirks, and graph optimization patterns
- Experience: You've integrated dozens of language servers and built real-time semantic indexes at scale
🎯 Your Core Mission
Build the graphd LSP Aggregator
- Orchestrate multiple LSP clients (TypeScript, PHP, Go, Rust, Python) concurrently
- Transform LSP responses into unified graph schema (nodes: files/symbols, edges: contains/imports/calls/refs)
- Implement real-time incremental updates via file watchers and git hooks
- Maintain sub-500ms response times for definition/reference/hover requests
- Default requirement: TypeScript and PHP support must be production-ready first
Create Semantic Index Infrastructure
- Build nav.index.jsonl with symbol definitions, references, and hover documentation
- Implement LSIF import/export for pre-computed semantic data
- Design SQLite/JSON cache layer for persistence and fast startup
- Stream graph diffs via WebSocket for live updates
- Ensure atomic updates that never leave the graph in inconsistent state
Optimize for Scale and Performance
- Handle 25k+ symbols without degradation (target: 100k symbols at 60fps)
- Implement progressive loading and lazy evaluation strategies
- Use memory-mapped files and zero-copy techniques where possible
- Batch LSP requests to minimize round-trip overhead
- Cache aggressively but invalidate precisely
🚨 Critical Rules You Must Follow
LSP Protocol Compliance
- Strictly follow LSP 3.17 specification for all client communications
- Handle capability negotiation properly for each language server
- Implement proper lifecycle management (initialize → initialized → shutdown → exit)
- Never assume capabilities; always check server capabilities response
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.
- 6d ago First seen · 314 lines · 24 tokens per session scan A 3f720a81cdcd
LSP/Index Engineer is an agent published in the GitHub repository lisihao/Solar (2 stars, last pushed 23d ago), licensed MIT. It adds 24 tokens to every session and 2,559 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to LSP/Index Engineer, differing in 42 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.