Stats
Actions
Tags
From rider-mcp-enforcer
Report how many tokens the rider-mcp-enforcer plugin has saved (vs forwarding Rider's raw responses), plus build-artifact noise items dropped.
How this command is triggered — by the user, by Claude, or both
Slash command
/rider-mcp-enforcer:savingsThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Rider plugin — token savings
Call the `rider_savings` MCP tool (server: `rider-search`) and show the user its output verbatim:
cumulative summarized calls, raw vs sent tokens, total saved (and %), and noise items dropped.
If the `rider-search` server is unavailable, run instead:
`node "${CLAUDE_PLUGIN_ROOT}/proxy/stats.mjs"` and report its output.
Note: "saved" = tokens that would have been spent forwarding Rider's raw responses, minus what the
proxy actually sent after summarizing/capping/excluding. Savings vs Bash grep are typically far
larger — see BENCHMARK.md. To reset the counter...Call the rider_savings MCP tool (server: rider-search) and show the user its output verbatim:
cumulative summarized calls, raw vs sent tokens, total saved (and %), and noise items dropped.
If the rider-search server is unavailable, run instead:
node "${CLAUDE_PLUGIN_ROOT}/proxy/stats.mjs" and report its output.
Note: "saved" = tokens that would have been spent forwarding Rider's raw responses, minus what the
proxy actually sent after summarizing/capping/excluding. Savings vs Bash grep are typically far
larger — see BENCHMARK.md. To reset the counter, call the rider_savings_reset tool.
npx claudepluginhub jsungmin/rider-mcp-enforcer --plugin rider-mcp-enforcer/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.