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 skills add Zfinix/aster --skill lsp-navigationgit clone --depth 1 https://github.com/Zfinix/asterWrote 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/skills/zfinix/aster/lsp-navigation)<a href="https://agentmods.dev/skills/zfinix/aster/lsp-navigation"><img src="https://agentmods.dev/badge/skills/zfinix/aster/lsp-navigation.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00384 |
| Opus 5 | $0.00026 | $0.00192 |
| Sonnet 5 | $0.00011 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
lsp-navigation 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 yesterday.
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
LSP navigation
- lsp_diagnostics beats a full build for "did my edit compile". After
editing a file, one diagnostics call answers it in milliseconds. A full
cargo checkortscrun is for the end of a task, not every edit. - lsp_references finds real usages. Text search finds the name in comments, strings, and unrelated scopes; references finds call sites. Use it before renaming or deleting anything. It takes a file plus a position, so search for the symbol first, then pass the position of one hit.
- lsp_definitions jumps to the source. Use it when a call site's types are unclear and you need the signature, instead of guessing the file path and reading it.
- Line and character are zero-based. The positions come from the file itself; if you just read the file, the line you saw is already the right number minus one.
- The first call in a language is slow. The server starts and indexes on first use; rust-analyzer can take seconds on a large crate. That is startup cost, not a hang. Subsequent calls in the same session reuse the running server.
- Missing servers are expected. If a tool says the language server is not installed, fall back to text search and a build; do not retry or tell the user to install anything unless they ask.
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.
- yesterday First seen · 28 lines · 53 tokens per session scan A 166741dd6e3f
lsp-navigation is a skill published in the GitHub repository Zfinix/aster (57 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 384 once invoked, about $0.0003 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-09-06.
Other skills, from other repositories
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
node-notready-triage
Use when nodes are NotReady or the whole cluster looks unhealthy — inspects node conditions, CNI/kube-system pods, and capacity to find what is keeping the kubelet or network from being ready.
pod-crashloop-triage
Use when pods are in CrashLoopBackOff, ImagePullBackOff, ErrImagePull, or OOMKilled — collects describe/logs/events and identifies the failure class before recommending a fix.
platform-sre-triage
Use when triaging platform reliability issues — orchestrates service health reporting, then Docker disk diagnostics, then the smallest safe next action.
ml-training-job-triage
Use when triaging failed, slow, or expensive ML training jobs, GPU utilization, data/input errors, checkpoints, and retry strategy.
speccrew-test-runner
SpecCrew Test Runner. Executes test code, parses results, and detects deviations between expected and actual outcomes. Reads test code files and system design to run platform-specific test suites.