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.
git clone --depth 1 https://github.com/ArtemioPadilla/agent-triforceWrote 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/artemiopadilla/agent-triforce/lsp-setup)<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/lsp-setup"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/lsp-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/lsp-setup"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/lsp-setup.svg" alt="Reviewed on agentmods" width="80" 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.00015 | $0.00437 |
| Opus 5.5 | $0.00006 | $0.00175 |
| Sonnet 5.5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
lsp-setup 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 1mo 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.
What it actually says
Set up LSP integration so that agents receive real compiler errors, type checker output, and lint warnings instead of relying on heuristic analysis.
Step 1: Detect project type
Scan the project root for these manifest files to determine the tech stack:
package.jsonortsconfig.json--> TypeScriptpyproject.toml,setup.py, orrequirements.txt--> PythonCargo.toml--> Rust
Step 2: Copy the appropriate template
Based on detected project type, copy the matching template to .lsp.json in the project root:
| Stack | Template | LSP Server |
|---|---|---|
| TypeScript | templates/lsp/typescript.lsp.json |
typescript-language-server |
| Python | templates/lsp/python.lsp.json |
pylsp |
| Rust | templates/lsp/rust.lsp.json |
rust-analyzer |
If the project uses multiple languages, merge the servers arrays from each template into a single .lsp.json.
Step 3: Verify LSP server is installed
Check if the required LSP server binary is available:
- TypeScript:
which typescript-language-server(install vianpm install -g typescript-language-server typescript) - Python:
which pylsp(install viapip install python-lsp-server[all]) - Rust:
which rust-analyzer(install viarustup component add rust-analyzer)
If not installed, provide the install command and ask the user to install it.
Step 4: Confirm setup
Report what was configured and remind the user:
- LSP diagnostics are per-project (
.lsp.jsonin project root) - If no LSP configuration exists, agents proceed normally with heuristic analysis
- Supported LSP servers in v1:
typescript-language-server,pylsp,rust-analyzer
Templates location: templates/lsp/
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.
- 1mo ago First seen · 43 lines · 15 tokens per session scan A 869de8dab559
lsp-setup is a command published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 437 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
scan
Populate the world model — the project's directories and files, stored as tables in the trajectory DB — by walking the project root for git repos and pulling each dir's README.md into a summary. Single phase — no background fill required for the primary navigation surface.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
ui-audit
Run comprehensive UI/UX design validation against design principles, accessibility standards, and usability laws.
chronicle
One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.
board-review
Quick board review - get expert opinions from 5 directors without full deliberation.
loop-plan-evaluator
Validate execution plan against spec. Evaluate-Loop Step 2.