From vs-token-safer
Report how many tokens the vs-token-safer plugin has saved (vs forwarding the language server's raw index responses).
How this command is triggered — by the user, by Claude, or both
Slash command
/vs-token-safer:savingsThe summary Claude sees in its command listing — used to decide when to auto-load this command
# vs-token-safer — token savings
Call the `vts_admin` MCP tool with `{ "op": "savings" }` (server: `vs-search`) and show the user its
output verbatim: cumulative searches, raw vs sent tokens, total saved (and %), and the biggest single run.
If the `vs-search` server is unavailable, run instead: `vts savings` and report its output.
Note: "saved" = tokens that would have been spent forwarding the language server's raw index
response, minus what the plugin actually sent after token-capping to `file:line`. Savings vs Bash
grep-and-paste are typically far larger. To reset the counter, call `v...Call the vts_admin MCP tool with { "op": "savings" } (server: vs-search) and show the user its
output verbatim: cumulative searches, raw vs sent tokens, total saved (and %), and the biggest single run.
If the vs-search server is unavailable, run instead: vts savings and report its output.
Note: "saved" = tokens that would have been spent forwarding the language server's raw index
response, minus what the plugin actually sent after token-capping to file:line. Savings vs Bash
grep-and-paste are typically far larger. To reset the counter, call vts_admin { "op": "savings_reset" }
(or vts savings-reset).
npx claudepluginhub jsungmin/vs-token-safer --plugin vs-token-safer/savingsDisplays a detailed savings report for dev-team-kit-fv, including tokens saved, cost avoided, bugs prevented, and gate decisions. Supports --since and --format arguments.
/savingsDisplays a dashboard of context-os token savings with all-time, weekly, and streak metrics. Also supports --card-only and --json flags.