usage-auditor

Summarize proxy usage data and forecast month-end spend against a monthly cap.

Updated May 22, 2026
One-click install
npx skills add https://github.com/asifhussain60/journal --skill usage-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: usage-auditor
Source: https://github.com/asifhussain60/journal/tree/main/skills-staging/usage-auditor
Command: npx skills add https://github.com/asifhussain60/journal --skill usage-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Summarizes monthly usage data and endpoint costs to help teams prevent overspending against a proxy's cap with a read-only audit.

Core Features & Use Cases

  • Read live usage summary from the proxy and per-endpoint costs to compute total spend, throttle events, and forecast month-end burn.
  • Support on-demand audits, monthly retrospectives, and cap-tuning workflows using embedded pricing.

Quick Start

Run usage-auditor for the current month to forecast end-of-month spend against the cap.

Frequently Asked Questions about usage-auditor

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

FAQPage Schema
How do I forecast end-of-month API spend against a usage cap?

You can forecast spend by auditing local telemetry and proxy stats to compute current burn and project month-end costs. This Skill uses embedded pricing and read-only data access to predict final invoices without external API calls.

What is the best way to audit usage data for monthly retrospectives?

Auditing usage for retrospectives involves summarizing live proxy telemetry and per-endpoint costs. This process calculates total spend and throttle events to help teams evaluate consumption patterns and prevent overload during future periods.

Can I use embedded pricing to calculate total endpoint costs without external APIs?

Yes, you can calculate endpoint costs using embedded pricing without external APIs. The audit relies entirely on local usage logs and fixed embedded rates to perform deterministic aggregation and compute your total spend.

How do I prevent overspending on a proxy cap during cap-tuning?

To prevent overspending during cap-tuning, run a read-only audit on live usage summaries to compare current burn rates against the configured proxy cap. This identifies throttle events and projects if month-end spend will breach the limit.

Does the usage audit require write access to proxy telemetry logs?

No, the usage audit operates entirely with read-only data access. It safely summarizes live usage logs and proxy stats to compute spend and forecast burn without modifying your telemetry records.