tokendiet
Related Servers
Alternatives to tokendiet
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to reduce token usage by condensing source code into AST skeletons, extracting specific symbols, compressing logs, and estimating token budgets.4MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to reduce token usage and context bloat through AST skeletonization, prompt distillation, caching, and token-budget governance while preserving essential code context.1311,938 npm7,114 PyPI46MIT
- AlicenseAqualityBmaintenanceEnables coding agents to reduce prompt token usage by extracting code skeletons and symbols, compressing test and command output, generating compact diffs, and tracking session token health to avoid rate-limit lockouts.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to shrink bulky tool output, logs, test runs, and file dumps down to compact briefs, and to record and recall decisions in a small session ledger. This keeps long-running tasks within context limits while preserving errors, findings, and key notes.8 npmMIT
- AlicenseBqualityCmaintenanceEnables coding agents to reduce context tokens by requesting file outlines, individual symbols, compact searches, and condensed test, lint, and type-check failures instead of reading whole files or raw command output.666 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables a coding agent to compress noisy tool output such as compiler errors, failing test runs and repeated logs before it enters the context window, and to fetch any collapsed ref back as its exact original text. Two tools, squeeze_fetch and squeeze_compress, keep the reduction reversible by the model itself.1MIT
TDQS
Scored across 4 tools
Each tool targets a distinct operation: log pruning, code skeletonization, session compression, and cost-tier routing. However, compress_session explicitly bundles log pruning and AST skeletonization, so its boundary with prune_tool_output and skeletonize_code is fuzzy—an agent may pick the narrower tool when the session-level one was intended (or vice versa).
All four tools share the tokendiet_ prefix and follow a consistent snake_case verb_noun pattern (prune_tool_output, skeletonize_code, compress_session, route_finops). The naming is predictable and readable.
Four tools is a lean, well-scoped surface where each tool maps to a distinct compression/routing concern, with no filler. It is slightly thin—nothing handles token counting or budget configuration—but nothing is redundant.
The set covers the main workflow: prune logs, skeletonize code, compress a full trace, and route to model tiers. It lacks a standalone token-count/budget-estimation utility and any way to inspect or tune pruning/skeletonization settings, which agents would likely want before committing to a compression budget.