token-watch

Monitors Claude account token quotas across multiple pools and reports estate status with rotation verdicts.

Updated May 12, 2026
One-click install
npx skills add https://github.com/fryanpan/ai-team-lead --skill token-watch-fryanpan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: token-watch
Source: https://github.com/fryanpan/ai-team-lead/tree/main/.claude/skills/token-watch
Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill token-watch-fryanpan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Running a fleet of Claude agents across multiple accounts makes it hard to know how much token quota remains, which pool is active, and when to rotate accounts before hitting a hard stop. This Skill turns scattered usage readings into a single estate table and one actionable verdict. ## Core Features & Use Cases - Estate-wide quota reporting: Reads live usage meters from every account pool and presents them in one table with runway, trust level, and reset times. - Trend logging: Appends a one-line entry per run to a trend log so quota burn can be tracked over days. - Rotation verdicts: Distinguishes normal burn from genuine Tier 2 rotation calls and re-pings open decisions as their projected date approaches. - Use Case: Three times a day, an automated check reads the active account's usage, records both weekly and session meters via fleet_budget_watch.py, and reports whether the current pool outlasts the next pool's reset or needs a rotation. ## Quick Start Ask the agent to run the token watch check and report the current estate status and rotation verdict.

Frequently Asked Questions about token-watch

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

FAQPage Schema
How do I check Claude account token usage across multiple accounts?▼

Read the live usage meter from an idle agent's pane, then record both the weekly and session percentages with fleet_budget_watch.py. The script prints an estate panel showing every pool's used percentage, runway, and reset time.

How to measure token burn rate for a Claude account pool?▼

Measure points gained on the active pool's own meter divided by elapsed hours since the stint began. Never divide used percentage by hours, since a pool re-entered mid-window produces inflated rates and false alerts.

Can I trust a previously recorded token usage figure?▼

No. An idle pool's meter can only rise until its reset, so a stale reading is a floor rather than a current value. Always pull the live meter and check account_since before quoting any written figure.

Why does piping script output to tail hide errors?▼

Piping to tail reports tail's exit status instead of the script's, so failures read as clean. Capture the exit code directly with cmd > f 2>&1; echo $? to detect drift check failures.

When should a token pool rotation be escalated?▼

Escalate rotation as a Tier 2 call only when the active pool will die before the next pool's reset, since rotation severs the claude.ai connector set fleet-wide. A pool trending to 100% under burn-freely rotation is expected, not an alert.