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 skills/youdotcom-oss/dx-toolkit/typescript-lspnpx skills add youdotcom-oss/dx-toolkit --skill typescript-lspgit clone --depth 1 https://github.com/youdotcom-oss/dx-toolkitWrote 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/youdotcom-oss/dx-toolkit/typescript-lsp)<a href="https://agentmods.dev/skills/youdotcom-oss/dx-toolkit/typescript-lsp"><img src="https://agentmods.dev/badge/skills/youdotcom-oss/dx-toolkit/typescript-lsp.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 | $0.00051 | $0.01439 |
| Opus 5 | $0.00026 | $0.00720 |
| Sonnet 5 | $0.00010 | $0.00288 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade A, and why
typescript-lsp 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 5d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript LSP Skill
Purpose
This skill provides TypeScript Language Server Protocol integration for exploring and understanding TypeScript/JavaScript codebases.
IMPORTANT: Prefer LSP tools over Grep/Glob when working with *.ts, *.tsx, *.js, *.jsx files. LSP provides type-aware results that understand imports, exports, and symbol relationships.
Use these tools to:
- Explore codebases - Find symbols, understand module structure, discover implementations
- Find references - Type-aware search across the entire codebase (better than grep for symbols)
- Understand types - Get full type signatures, generics, and documentation
- Verify before editing - Check all usages before modifying or deleting exports
- Navigate code - Jump to definitions, find implementations
When to Use Each Tool
| Tool | LSP Method | Purpose |
|---|---|---|
| Glob | — | Find files by pattern |
| Grep | — | Search text content |
workspace/symbol |
symbol search | Find a TypeScript symbol by name across the workspace |
textDocument/hover |
hover | Get type signature + TSDoc at a position |
textDocument/references |
references | Find all usages of a symbol |
textDocument/documentSymbol |
doc symbols | List all symbols in a file |
LSP vs Grep/Glob
| Task | Use LSP | Use Grep/Glob |
|---|---|---|
| Find all usages of a function/type | ✅ textDocument/references |
❌ Misses re-exports, aliases |
| Search for a symbol by name | ✅ workspace/symbol |
❌ Matches strings, comments |
| Get type signature + TSDoc | ✅ textDocument/hover |
❌ Not possible |
| List all symbols in a file | ✅ textDocument/documentSymbol |
❌ Doesn't resolve re-exports |
| Find files by pattern | ❌ | ✅ Glob |
| Search non-TS files (md, json) | ❌ | ✅ Grep |
| Search for text in comments/strings | ❌ | ✅ Grep |
When to Use
Exploring code (prefer LSP):
workspace/symbolto search for a symbol by name across the workspacetextDocument/documentSymbolto get an overview of all symbols in a filetextDocument/hoverto get the exact type signature at a position
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.
- 5d ago First seen · 162 lines · 51 tokens per session scan A a2b87629a799
typescript-lsp is a skill published in the GitHub repository youdotcom-oss/dx-toolkit (25 stars, last pushed 15d ago), licensed MIT. It adds 51 tokens to every session and 1,439 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-08-30.
Other skills, from other repositories
build-cli
Build the unity-mcp-cli TypeScript CLI tool and link it globally for terminal use.
add-export
Add a new subpath export to the @cyanheads/mcp-ts-core package. Use when creating a new public API surface that consumers import from a dedicated subpath (e.g., @cyanheads/mcp-ts-core/newutil).
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
reflection-method-call
Call a C# method by reflection — including private methods. Requires a method schema obtained via 'reflection-method-find'. Supports static methods, instance methods (with optional target deserialization), and main-thread / off-thread execution.