skills.rest
Jamkris
JamkrisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

context-budget

Audit token overhead across Gemini CLI components and deliver a prioritized improvement roadmap.

86|21|Updated Feb 9, 2026
Search Tags:#context#optimization#cli#gemini#budget#analyze#token
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill context-budget-jamkris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-budget
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/context-budget
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill context-budget-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gemini CLI sessions accumulate contextual tokens from multiple components (agents, skills, MCP servers, rules, and GEMINI.md), causing bloated prompts and slower responses. This skill identifies where token waste occurs and delivers a prioritized plan to reclaim headroom.

Core Features & Use Cases

  • Phase-based analysis across Agents, Skills, Rules, MCP servers, and GEMINI.md to quantify token usage.
  • Heuristic flags for heavy files and bloated frontmatter to flag optimization targets.
  • Budget reporting that surfaces actionable token-savings recommendations ranked by impact.
  • Use Case: planning to add more components and wanting to ensure there is context headroom.

Quick Start

Run the /egc-context-budget command to generate the context budget report for your current Gemini session.

Frequently Asked Questions about context-budget

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token usage in my Gemini CLI sessions?▼

To reduce token usage in Gemini CLI sessions, you need to audit context bloat across agents, skills, MCP servers, rules, and GEMINI.md. This skill identifies where token waste occurs and delivers a prioritized plan to reclaim headroom.

What causes context bloat in Gemini CLI prompts?▼

Context bloat in Gemini CLI is caused by accumulated tokens from multiple components like agents, skills, MCP servers, rules, and GEMINI.md. Heavy files and bloated frontmatter are common culprits that slow down responses.

How do I analyze token overhead across Gemini CLI components?▼

You can analyze token overhead by running a phase-based analysis across Agents, Skills, Rules, MCP servers, and GEMINI.md. This generates a budget report with heuristic flags for heavy files and actionable recommendations ranked by impact.

Can I check if my Gemini session has enough context headroom before adding new components?▼

Yes, you can check context headroom before adding new components by generating a context budget report. This analyzes per-component token estimates and SKILL.md frontmatter to ensure you have enough space for planned additions.

What is the best way to find token waste in GEMINI.md and MCP servers?▼

The best way to find token waste is to use a budget reporting tool that surfaces heuristic flags for bloated frontmatter and heavy files. It quantifies token usage across components and provides a concise improvement roadmap.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
rocklambrosrocklambros
2

auditing-instruction-hierarchy

Audits CLAUDE.md hierarchies for size, cache hygiene, and scope drift.

Community
Advanced
llmh333llmh333

context-budget

Analyze Gemini CLI token consumption across agents, skills, rules, and MCP servers.

Community
Advanced
ArogyaReddyArogyaReddy
1

token-audit

Audit Claude Code configuration files to measure fixed-context token overhead.

Community
Advanced