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.
/plugin marketplace add anthropics/claude-plugins-officialnpx agentmods add plugins/anthropics/claude-plugins-official/typescript-lspgit clone --depth 1 https://github.com/anthropics/claude-plugins-officialWrote 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/plugins/anthropics/claude-plugins-official/typescript-lsp)<a href="https://agentmods.dev/plugins/anthropics/claude-plugins-official/typescript-lsp"><img src="https://agentmods.dev/badge/plugins/anthropics/claude-plugins-official/typescript-lsp.svg" alt="Measured on agentmods" height="20"></a>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 today.
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
{
"name": "typescript-lsp",
"description": "TypeScript/JavaScript language server for enhanced code intelligence",
"version": "1.0.0",
"author": {
"name": "Anthropic",
"email": "[email protected]"
},
"source": "./plugins/typescript-lsp",
"category": "development",
"strict": false,
"lspServers": {
"typescript": {
"command": "typescript-language-server",
"args": [
"--stdio"
],
"extensionToLanguage": {
".ts": "typescript",
".tsx": "typescriptreact",
".js": "javascript",
".jsx": "javascriptreact",
".mts": "typescript",
".cts": "typescript",
".mjs": "javascript",
".cjs": "javascript"
}
}
}
}What ships with it
1 file beside marketplace.json#typescript-lsp in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 30 lines scan A f711d36e3141
typescript-lsp is a plugin published in the GitHub repository anthropics/claude-plugins-official (35,867 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
skills
Modern Deno development knowledge: dependency management, npm and JSR packages, permissions, the built-in toolchain, migrating from Node/npm/yarn/pnpm/bun, Fresh, and Deno Deploy.
ts7-lsp
TypeScript/JavaScript code intelligence via the TypeScript 7 native compiler LSP, much faster than tsserver on large monorepos.
solana-kit
Modern tree-shakeable JavaScript SDK from Anza with zero dependencies and full TypeScript support.
solana-kit-migration
Migration guide between @solana/web3.js v1.x and @solana/kit with API mappings.
package-architect
Design and maintain TypeScript packages in a monorepo, including exports and build configuration. Use when creating or restructuring monorepo packages, defining package.json exports, or setting up tsconfig references.
typescript-expert
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between…