dce
01Command
Part of vs-token-safer
Preview-only dead-code analysis — from a seed symbol, walk the call graph to a fixpoint and list what is provably DEAD (and what cascades), without deleting anything.
Token-saving code search for AI coding agents — TypeScript, JavaScript & Python (zero setup), C#, C++, Go & 30+ more, via a language-server or tree-sitter index instead of grep. Local-only, no IDE. Claude Code plugin + MCP + CLI.
Command
Part of vs-token-safer
Preview-only dead-code analysis — from a seed symbol, walk the call graph to a fixpoint and list what is provably DEAD (and what cascades), without deleting anything.
Command
Part of vs-token-safer
Report how many tokens the vs-token-safer plugin has saved (vs forwarding the language server's raw index responses).
Command
Part of vs-token-safer
Configure the vs-token-safer plugin (project path, backend, result cap). Writes /.vs-token-safer/config.json and tells you to /reload-plugins.
Command
Part of vs-token-safer
Refresh the committable tree-sitter symbol index (.vts-index) when it has gone STALE — one incremental re-index so the syntactic tier answers CURRENT code, not the state it was built at. Use when searchsymbol shows "SYNTACTIC · STALE", after a big branch switch / pull / large refactor, or when the file:line answers…
Command
Part of vs-token-safer
Stop the vs-token-safer dashboard server started by /vs-token-safer:viz (frees the port; nothing was ever transmitted).
Command
Part of vs-token-safer
Open the vs-token-safer dashboard — a local (127.0.0.1, nothing transmitted) page showing tokens saved, language mix, per-tool savings, and the include graph as an interactive 3D force graph (Three.js, vendored locally — no CDN).
Command
Part of gamedev-log-analyzer
Scan local Claude Code transcripts and report (aggregate, local-only) how many raw log reads bypassed gamedev-log vs went through it — to find missed token savings. No log content in the output.
Command
Part of gamedev-log-analyzer
Show or set Bash log-grep enforcement (block / warn / off) — controls whether raw grep/tail/cat over .log/.jsonl/Logs is intercepted and steered to gamedev-log.
Command
Part of gamedev-log-analyzer
Analyze the game-engine/build log (Unreal Saved/Logs, Unity Editor.log, Godot output, MSVC/UBT/MSBuild, or any structured log) — parse, deduplicate, classify by severity/category, and read it token-efficiently via the gamedev-log CLI instead of dumping the raw file.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: