token-tracker

Measure router-level token efficiency and enforce API budget alerts.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/CivicOSInstitute/civicos-institute.github.io --skill token-tracker-civicosinstitute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-tracker
Source: https://github.com/CivicOSInstitute/civicos-institute.github.io/tree/main/skills/token-tracker
Command: npx skills add https://github.com/CivicOSInstitute/civicos-institute.github.io --skill token-tracker-civicosinstitute

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Router-centric telemetry and budgeting to optimize API usage and reduce waste across routing decisions.

Core Features & Use Cases

  • Tracks route tiers (T0/T1/T2) to quantify routing efficiency.
  • Measures cache hits, compression ratios, quality pass rate, and token totals for cost control.
  • Use case: teams deploying API gateways can monitor monthly usage and adjust budgets to stay under limits.

Quick Start

Log a routed task with token-tracker log and then check status to view the latest efficiency metrics.

Frequently Asked Questions about token-tracker

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

FAQPage Schema
How do I track API gateway routing efficiency and token costs?

To track API gateway routing efficiency and token costs, you ingest local telemetry from routed tasks, computing per-event metrics like routing tier, cache hits, latency, and compression ratios to minimize unnecessary API calls.

What metrics are used to measure router-level efficiency for LLM providers?

Router-level efficiency for LLM providers is measured by tracking routing tiers (T0/T1/T2), cache hit rates, compression ratios, quality pass rates, and latency to quantify routing performance and identify wasted token usage.

How can I enforce API token budgets and set up cost alerts?

You can enforce API token budgets by logging routed tasks to compute monthly usage, enabling budget alerts and usage forecasting to ensure your API gateway deployments stay under defined cost limits.

Does this telemetry approach work for edge services managing API gateways?

Yes, this telemetry approach works for edge services managing API gateways by applying local telemetry ingestion to monitor routing tiers, cache performance, and cost across distributed routing decisions.

What is the best way to monitor monthly API usage and reduce wasted token calls?

The best way to monitor monthly API usage and reduce wasted token calls is to log routed tasks and check status to view the latest efficiency metrics, adjusting budgets based on computed per-event costs.