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/okhp3/skillz/lsp-dead-codenpx skills add OKHP3/skillz --skill lsp-dead-codegit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/lsp-dead-code)<a href="https://agentmods.dev/skills/okhp3/skillz/lsp-dead-code"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/lsp-dead-code.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.00043 | $0.02172 |
| Opus 5 | $0.00022 | $0.01086 |
| Sonnet 5 | $0.00009 | $0.00434 |
| Haiku 4.5 | $0.00004 | $0.00217 |
Grade A, and why
lsp-dead-code 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 yesterday.
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.
This is a copy
100% identical to lsp-dead-code — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requires the agent-lsp MCP server.
lsp-dead-code
Audit an exported symbol list for zero-reference candidates. Calls
list_symbols to enumerate symbols, then checks each exported
symbol with find_references to find callers. Produces a classified report.
When to Use
Use this skill when you want to identify dead code in a file — exported symbols that are defined but never called anywhere in the workspace. Common use cases:
- Cleaning up APIs before a release
- Identifying legacy exports that can be safely removed
- Auditing a package for unused public surface area
Important: This skill surfaces candidates. Always review results manually before deleting anything. See the Caveats section below.
What counts as "exported"
| Language | Exported means... |
|---|---|
| Go | Identifier starts with an uppercase letter (e.g. MyFunc, MyType) |
| TypeScript | Has export keyword; or is a public class member (no private) |
| Python | Not prefixed with _; or explicitly listed in __all__ |
| Java/C# | Has public or protected visibility modifier |
| Rust | Has pub keyword |
Prerequisites
If LSP is not yet initialized, call mcp__lsp__start_lsp with the
workspace root first:
mcp__lsp__start_lsp({ "root_dir": "/your/workspace" })
agent-lsp supports auto-inference from file paths, so explicit start is only required when switching workspaces or on a cold session.
Step 0 — Verify indexing is complete (mandatory)
Do not skip this step. An under-indexed workspace returns [] for
symbols that ARE referenced, producing false dead-code candidates.
Pick one symbol you know is actively used (e.g. the primary constructor,
a widely-called utility function). Call find_references on it:
What ships with it
1 file beside SKILL.md 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.
- yesterday First seen · 237 lines · 43 tokens per session scan A 60e24a2da4d8
lsp-dead-code is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 2,172 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to lsp-dead-code, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
vastai-sdk
Vast.ai Python SDK — high-level API for GPU instances, volumes, serverless endpoints, and billing.
pm-aarrr
Use when: 产品上线后需要分析用户增长、制定增长策略、诊断产品健康度、优化AARRR各环节 Do NOT use when: 产品未上线、仅需单一指标分析无需全链路.
pm-docs
Use when: 需要输出PRD/BRD/MRD产品文档、方案文档、商业计划文档、需要文档模板 Do NOT auto-select when: 用户用自然语言说"写需求文档""写PRD""帮我设计需求"等新产品请求 → 这些必须先路由到 start-super-pm Direct slash-command use is allowed: 用户显式输入 /pm-docs 时可直接进入，但必须通过本 skill 的前置门禁 Do NOT use when: 文档已完备无需生成、仅需口头讨论无需书面输出.
pm-position
Use when: 需要明确产品定位、设计商业模式、规划盈利方式、制定定价策略、进行盈利预测 Do NOT use when: 产品定位已明确、仅需执行无需重新定位.
pm-retro
Use when: 迭代结束后需要复盘总结经验教训、改进团队流程、记录改进行动项 Do NOT use when: 迭代尚未结束、团队不需要正式复盘.
product-marketing-copywriter
当市场调研分析师与营销专员、内容创作者需要推广产品时，使用本技能可精准分析受众痛点与产品卖点，一键生成高转化标题与正文，快速产出激发购买欲的优质营销文案，大幅提升销售转化率。.