Skip to content
Back to skills

Track Coding Agent Quota Burn And Remaining Headroom Across Providers With Onwatch

ASecurity

Monitor quota, spend, resets, and alerts across multiple coding-agent providers from one local dashboard before a long run hits throttling or budget limits.

  • 36 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 8, 2026
ai-agentsgoshelldockergitapisecuritydocumentation

Works with

  • api

Security analysis

A100/100

Scanned June 8, 2026

npx -y skills add agentskillexchange/skills --skill track-coding-agent-quota-burn-and-remaining-headroom-across-providers-with-onwatch --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Track Coding Agent Quota Burn And Remaining Headroom Across Providers With Onwatch?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Track Coding Agent Quota Burn And Remaining Headroom Across Providers With Onwatch
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agentskillexchange-track-coding-agent-quota-burn-and-remaining-headro/badge)](https://www.skillsdirectory.com/skills/agentskillexchange-track-coding-agent-quota-burn-and-remaining-headro)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "Track coding-agent quota burn and remaining headroom across providers with onWatch"
slug: "track-coding-agent-quota-burn-and-remaining-headroom-across-providers-with-onwatch"
description: "Monitor quota, spend, resets, and alerts across multiple coding-agent providers from one local dashboard before a long run hits throttling or budget limits."
github_stars: 580
verification: "security_reviewed"
source: "https://github.com/onllm-dev/onWatch"
author: "onllm-dev"
publisher_type: "organization"
category: "Monitoring & Alerts"
framework: "Multi-Framework"
tool_ecosystem:
  github_repo: "onllm-dev/onWatch"
  github_stars: 580
---

# Track coding-agent quota burn and remaining headroom across providers with onWatch

Monitor quota, spend, resets, and alerts across multiple coding-agent providers from one local dashboard before a long run hits throttling or budget limits.

## Prerequisites

onWatch binary or Homebrew install, local shell access, provider credentials for one or more supported services, and optional browser access for the local dashboard

## Installation

Use the upstream install or setup path that matches your environment:
- docker run -d --name onwatch -p 9211:9211 \
- git clone https://github.com/onllm-dev/onwatch.git && cd onwatch
- docker-compose up -d
- docker-compose logs -f

Requirements and caveats from upstream:
- | GEMINI_REFRESH_TOKEN | Gemini OAuth refresh token (for Docker/headless) |
- | GEMINI_ACCESS_TOKEN | Gemini OAuth access token (for Docker/headless) |
- | ANTIGRAVITY_BASE_URL | Antigravity base URL (for Docker/manual config) |

Basic usage or getting-started notes:
- Track usage across [Synthetic](https://synthetic.new), [Z.ai](https://z.ai), [Anthropic](https://anthropic.com), [Codex](https://openai.com/codex), [GitHub Copilot](https://github.com/features/copilot), [MiniMax](http...
- See history, get alerts, and open a local web dashboard before you hit throttling or run over budget. Additionally, you can ingest local telemetry from your own API-driven workflows with API Integrations, keeping trac...
- onWatch fills the gap between "current usage snapshot" and the historical, per-cycle, cross-session view that developers actually need. It runs as a lightweight background agent (<50 MB RAM with all nine providers pol...

- Source: https://github.com/onllm-dev/onWatch
- Extracted from upstream docs: https://raw.githubusercontent.com/onllm-dev/onWatch/HEAD/README.md

## Documentation

- https://onwatch.onllm.dev

## Source

- [Agent Skill Exchange](https://agentskillexchange.com/skills/track-coding-agent-quota-burn-and-remaining-headroom-across-providers-with-onwatch/)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.