Claude Code Plugins Expose Context Costs
Claude Code now documents how plugins consume always-on and per-invocation context, even when their skills or agents never run. Developers can inspect usage, identify stale plugins, and disable or uninstall them to reclaim budget and reduce attack surface.
Plugin ecosystems are becoming context-budget ecosystems: every convenience carries a persistent tax, so visibility and cleanup are essential.
- –Skill, agent, and command descriptions enter context on every turn; full component content loads only when invoked.
- –`claude plugin details` separates always-on tokens from per-invocation costs, while official marketplace listings expose estimates before installation.
- –`/plugin`, `/skill-doctor`, `/doctor`, and `/usage` help locate unused or expensive extensions; plugins unused for 14 days across 10 sessions are flagged.
- –MCP servers and hooks can run with the user’s permissions, making plugin review a security task as well as a cost-optimization task.
- –For teams, OpenTelemetry and Anthropic’s Analytics API extend plugin usage measurement across organizational deployments.
DISCOVERED
1h ago
2026-10-10
PUBLISHED
1h ago
2026-10-10
RELEVANCE
AUTHOR
DIY Smart Code