Analyze Forge token tracking and session logs to recommend configuration changes.
npx skills add https://github.com/lpjhelder/kronon-forge --skill help-lpjhelder
Please help me install this Agent Skill. Skill: help Source: https://github.com/lpjhelder/kronon-forge/tree/main/skills/help Command: npx skills add https://github.com/lpjhelder/kronon-forge --skill help-lpjhelder
Forge users often lack visibility into how Kronon/Forge commands consume tokens, which agents are most active, and which features are underutilized, leading to inefficient workflows and avoidable costs. This Skill centralizes usage telemetry analysis so you can identify costly patterns, missing practices like team usage, and misconfigured defaults that waste time or tokens.
Analyze my Forge usage and recommend token-saving settings and workflow improvements.
High-intent search queries and answers about installing and using this skill.
Analyze Forge session logs by reading local token-tracking and session-history files to identify inefficient workflows and high-cost model usage. This retrospective analysis reveals underutilized features like ecomode and suggests configuration changes to lower operational costs.
Check token consumption by aggregating Forge usage telemetry from session-history and token-tracking data. This summarizes total records, top active agents, and model distribution to pinpoint high-cost usage patterns and misconfigured defaults.
Forge stores session history and token tracking data locally in ~/.forge/state/session-history.json and ~/.forge/state/token-tracking.jsonl. These files capture agent usage, model distribution, and session metadata required for retrospective analysis.
Configurations that optimize token usage include setting defaultExecutionMode, adopting ecomode, and adding review agents. Analyzing your session logs provides concrete recommendations for applying these specific configuration changes to reduce costs.
You can still use usage analysis with missing data because the tool provides graceful degradation. It delivers clear messaging and next steps to help you enable tracking and rerun the analysis when token or session data is absent.
Forge usage analysis requires read access to token-tracking and session history files, and optionally reads ~/.kronon/.forge-config.json. This access is needed to compute agent counts, detect high-cost models, and produce concrete operational recommendations.
pextacyAnalyze OMX usage data and generate structured recommendations reports.
lpjhelderDisplay Forge orchestration HUD and Kronon status line from .forge state files.
lpjhelderOptimizes agent-workflow task routing across LOW, MEDIUM, and HIGH tiers to conserve tokens.
ChintanTurakhiaAnalyze Claude Code token usage and costs from local session data.
