Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/blackwell-systems/agent-lsp/lsp-architecture)<a href="https://agentmods.dev/skills/blackwell-systems/agent-lsp/lsp-architecture"><img src="https://agentmods.dev/badge/skills/blackwell-systems/agent-lsp/lsp-architecture/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/skills/blackwell-systems/agent-lsp/lsp-architecture"><img src="https://agentmods.dev/badge/skills/blackwell-systems/agent-lsp/lsp-architecture.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.00000 | $0.02287 |
| Opus 5 | $0.00000 | $0.01144 |
| Sonnet 5 | $0.00000 | $0.00457 |
| Haiku 4.5 | $0.00000 | $0.00229 |
Grade A, and why
lsp-architecture 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- lsp-architecture — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requires the agent-lsp MCP server.
lsp-architecture
Generate a structural architecture overview of any codebase: language distribution, package hierarchy, entry points, dependency flow, and hotspot files. One invocation for the big picture.
Read-only; does not modify any files.
Invocation: User provides the workspace root path (e.g.
"/home/user/myproject"). If omitted, use the current working directory.
Depth Controls (hard limits)
These limits are strict constraints. Never exceed them:
- Package enumeration: cap at 30 packages
- Hotspot analysis: cap at 10 files
- Workspace symbol queries: cap at 5 queries
- Do NOT recurse into
vendor/,node_modules/,.git/, or other dependency directories
Step 0 — Initialize
If LSP is not yet running, start it with the workspace root:
mcp__lsp__start_lsp({
"workspace_root": "<workspace-root>"
})
Then detect which language servers are available:
mcp__lsp__detect_lsp_servers({
"workspace_root": "<workspace-root>"
})
→ returns: list of detected servers with language names and file patterns
Record the available languages and their file globs. This determines which queries to run in later steps.
Step 1 — Language Detection
Scan the workspace to determine language distribution. Use file extension counts from the detected servers and supplement with a filesystem scan (via Glob tool) to count files per language.
For each detected language, report:
- Language name
- File count
- Estimated lines of code (sample 3-5 representative files and extrapolate)
Skip files in vendor/, node_modules/, .git/, dist/, build/, and
other common dependency or output directories.
Step 2 — Package Structure
Use find_symbol with broad queries to discover the package and
module hierarchy. Tailor queries by language:
Go:
mcp__lsp__find_symbol({
"query": "",
"symbol_kind_filter": "Package"
})
Also query for top-level types and functions to fill in package-level detail:
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.
- 10d ago First seen · 325 lines · 0 tokens per session scan A 2b4b6870baa7
lsp-architecture is a skill published in the GitHub repository blackwell-systems/agent-lsp (124 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,287 tokens. 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 skills, from other repositories
sem
Use sem to get entity-level (function/class/method) semantic diffs, impact analysis, blame, and dependency context from any Git repo. Trigger this skill whenever the user asks what changed in a commit or PR, wants to understand the blast radius of a change, needs to know who last modified a function, wants to trace…
sem
Semantic version control CLI. Entity-level diffs for Git (functions, classes, methods instead of lines).
trace-mcp-refactoring
Safe refactoring workflow using trace-mcp — assess risk, find candidates, check impact, and rename symbols across all files without missing import sites or cross-file references.
change-review
Use when reviewing a set of changes before they merge — a PR, a branch diff, or the working-tree changes you just made — in a Repowise-indexed codebase (.repowise/ directory exists). Activates for "review this PR", "is this safe to merge", "what's the blast radius of these changes", "did I miss anything", or "what…
code-health
Use when the user asks about code health, code quality, complexity, technical debt, which files are risky or hard to maintain, what to refactor next, untested hotspots, or coverage gaps in a Repowise-indexed codebase (.repowise/ directory exists). Also use to get a before/after health read when planning or finishing a…
authoring-smell-rules
Add a findsmells rule to mache — a SQL query over the projected code graph that surfaces a code smell (duplication, complexity, dead code, drift). Use when adding or debugging a SmellRule in cmd/smellrules.go or an external $MACHESMELLRULESDIR rule. Covers the SmellRule struct, the standalone-vs-ast table capability…