Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vynazevedo/first-plan/plugin install fpWrote 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/commands/vynazevedo/first-plan/lsp-status)<a href="https://agentmods.dev/commands/vynazevedo/first-plan/lsp-status"><img src="https://agentmods.dev/badge/commands/vynazevedo/first-plan/lsp-status.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.00030 | $0.01143 |
| Opus 5 | $0.00015 | $0.00571 |
| Sonnet 5 | $0.00006 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
lsp-status 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fp:lsp-status
Inspeciona Language Server Protocol no ambiente atual. Reporta servers detectados em PATH, versoes, cobertura no projeto e sugestoes de instalacao.
Workflow
Passo 1 - Engine check
Verificar se first-plan-engine esta disponivel:
ENGINE=$(which first-plan-engine 2>/dev/null || echo "${CLAUDE_PLUGIN_ROOT}/engine/bin/first-plan-engine")
if [ ! -x "$ENGINE" ]; then
echo "Engine nao encontrado. /fp:lsp-status requer engine binario >= v0.6.0"
exit 0
fi
Passo 2 - Status
"$ENGINE" lsp status --root "$PWD" --json > /tmp/lsp-status.json
"$ENGINE" lsp daemon status --json > /tmp/lsp-daemon.json
JSON retornado:
{
"engine_version": "0.6.0",
"project_root": "/path/to/project",
"project_needs": ["rust-analyzer", "typescript-language-server"],
"servers": [
{
"id": "RustAnalyzer",
"name": "rust-analyzer",
"language": "Rust",
"binary": "rust-analyzer",
"installed": true,
"path": "/home/user/.cargo/bin/rust-analyzer",
"version": "rust-analyzer 0.3.2127",
"install_cmd": "rustup component add rust-analyzer"
}
]
}
Passo 3 - Apresentar
=== LSP servers (8 suportados) ===
Status:
[OK] rust-analyzer Rust (path: ~/.cargo/bin/rust-analyzer)
[--] gopls Go install: go install golang.org/x/tools/gopls@latest
[--] pyright Python install: npm install -g pyright
[OK] typescript-language-server TypeScript/JavaScript (path: /usr/local/bin/typescript-language-server)
[--] intelephense PHP install: npm install -g intelephense
[OK] clangd C/C++ (path: /usr/bin/clangd)
[--] ruby-lsp Ruby install: gem install ruby-lsp
[--] lua-language-server Lua install: brew install lua-language-server
Projeto atual:
Stacks detectadas via manifests: Rust (Cargo.toml), TypeScript (package.json)
rust-analyzer: OK (cobertura 100%)
typescript-language-server: OK (cobertura 100%)
Recomendacoes:
Nenhuma - todos os servers necessarios estao instalados.
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 · 147 lines · 30 tokens per session scan A fb0ce65a1144
lsp-status is a command published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 11d ago), licensed MIT. It adds 30 tokens to every session and 1,143 once invoked, about $0.0002 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 commands, from other repositories
gradle-build
Fix Gradle build errors for Android and KMP projects.
views
Create Django views with proper structure and best practices.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.
subagent-execute
Execute a reviewed HOTL workflow in this session with delegated subagent steps and controller-owned verification.
execute-plan
Execute plan linearly with explicit human checkpoints.
kaeru
kaeru re-entry ritual — load process state + epistemic state for an initiative.