You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Token Consumption Analysis and Requirement for a Plugin Disable Feature for Agents #9858
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Description
This analysis documents the static token costs introduced by various permissions and the @tarquinen/[email protected] plugin. Tests indicate that even a tool designed for token optimization creates a significant overhead on its own.
Test Methodology & Findings
Agent State: Empty / Clean installation.
Input Prompt: "hi"
Observation: It has been observed that the @tarquinen/[email protected] plugin does not provide the expected optimization on the default system configuration; on the contrary, it causes high token consumption (790 tokens).
Contradictory Situation: The fact that a "token reduction tool" itself consumes 790 tokens leads to inefficient token usage.
Ineffectiveness: It has been confirmed that the tool fails to deliver the promised performance or savings on the default system.
Proposed Action (Feature Request)
A plugin disable feature for agents should be implemented to allow the plugin to be completely deactivated. This will provide users with the ability to manually intervene in scenarios where the optimization is ineffective or where the plugin's own cost outweighs its savings.
These issues all relate to giving users control over which plugins and tools are loaded to manage token consumption and overhead. Your analysis provides valuable data about static token costs that supports the need for these features.
Feel free to ignore if your specific use case differs from these.
Activity
github-actions commentedon Jan 21, 2026
This issue might be a duplicate of existing issues. Please check:
These issues all relate to giving users control over which plugins and tools are loaded to manage token consumption and overhead. Your analysis provides valuable data about static token costs that supports the need for these features.
Feel free to ignore if your specific use case differs from these.
github-actions commentedon Mar 28, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.