copilot-usage-analytics

Analyzes GitHub Copilot CLI sessions to estimate costs and recommend model routing strategies.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ivegamsft/work-tracker --skill copilot-usage-analytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-usage-analytics
Source: https://github.com/ivegamsft/work-tracker/tree/main/.agents/skills/copilot-usage-analytics
Command: npx skills add https://github.com/ivegamsft/work-tracker --skill copilot-usage-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps estimate Copilot CLI session costs, analyze model efficiency, and track dispatch patterns for GitHub Copilot usage.

Core Features & Use Cases

  • Cost Estimation: Estimate session costs from dispatch patterns.
  • Model Efficiency Analysis: Recommend model-routing strategies based on task complexity.
  • API Documentation: Map the current state of GitHub Copilot usage APIs.
  • Use Case: For instance, analyze which model is consuming the most tokens and recommend a more cost-effective model for a given task.

Quick Start

Use the copilot-usage-analytics skill to estimate the cost of the last Copilot CLI session.

Frequently Asked Questions about copilot-usage-analytics

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

FAQPage Schema
How do I estimate GitHub Copilot CLI session costs from usage logs?

To estimate Copilot CLI session costs, analyze dispatch patterns within your session logs to calculate token consumption and map it to pricing data.

What is model routing efficiency analysis for GitHub Copilot?

Model routing efficiency analysis evaluates task complexity within Copilot session logs to recommend the most cost-effective model routing strategies for your specific workflow.

Do I need specific API endpoints to track Copilot dispatch patterns?

Yes, tracking Copilot dispatch patterns requires access to GitHub Copilot usage API endpoints and session logs to accurately map and analyze your session token consumption.

How do I map the current state of GitHub Copilot usage APIs?

You can map GitHub Copilot usage APIs by documenting available API endpoints and their responses to establish the current state of usage data retrieval for analysis.

Can I analyze which Copilot model is consuming the most tokens?

Yes, you can analyze Copilot model efficiency by evaluating session logs to identify which model consumes the most tokens and subsequently recommend a more cost-effective alternative.

What data is needed to recommend cost-effective Copilot model strategies?

Recommending cost-effective Copilot model strategies requires session logs containing dispatch patterns, task complexity data, and current cost data retrieved from your API endpoints.