Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Monitor Kimi K2.5 API usage and quota from the Kimi console. Use when the agent needs to (1) Check remaining usage percentage and reset timers, (2) Make autonomous decisions about task prioritization based on available quota, (3) Monitor rate limit status before starting intensive operations, (4) Log usage patterns over time for resource planning. Essential for self-managing agents operating under quota constraints.
Monitor Kimi K2.5 API usage and quota from the Kimi console. Use when the agent needs to (1) Check remaining usage percentage and reset timers, (2) Make autonomous decisions about task prioritization based on available quota, (3) Monitor rate limit status before starting intensive operations, (4) Log usage patterns over time for resource planning. Essential for self-managing agents operating under quota constraints.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Monitor Kimi K2.5 usage quotas from the Kimi console to make informed decisions about task prioritization and resource allocation.
Before intensive operations: Check quota before starting multi-step research or coding tasks Autonomous planning: Self-prioritize tasks based on remaining usage percentage Rate limit awareness: Know when quotas reset to time high-priority work Usage tracking: Log patterns for long-term capacity planning
Prerequisites: Chrome with OpenClaw extension attached Open Chrome โ https://www.kimi.com/code/console?from=membership Click OpenClaw extension icon (badge should show ON) Ensure you're logged into Kimi # Check current usage (Linux/macOS/WSL) ./check_usage.sh # Windows native check_usage.bat # CMD .\check_usage.ps1 # PowerShell # JSON output for automation (all platforms) python3 scripts/fetch_usage.py --json Platform Support: Linux โ | macOS โ | Windows (WSL) โ | Windows (Native) โ
The Kimi console shows: MetricDescriptionDecision ThresholdWeekly UsagePercentage of weekly quota consumed>75% = prioritizeWeekly ResetHours until quota resetsPlan heavy tasks after resetRate LimitAdditional rate limiting quotaSecondary resourceRate ResetHours until rate limit resetsShort-term buffer
When operating autonomously, use these heuristics: ๐ข High Capacity (>50% remaining) Proceed with full capability Accept multi-step research tasks Spawn subagents as needed Enable verbose reasoning ๐ก Moderate Capacity (25-50% remaining) Batch similar operations Prefer concise outputs Use subagents sparingly Disable non-essential reasoning ๐ด Low Capacity (<25% remaining) Essential tasks only Single-step operations Avoid subagent spawning Prioritize user-directed work over proactive tasks
Before spawning subagents or starting multi-step tasks, check capacity: # Check if operation should proceed python3 scripts/preflight_check.py [light|standard|intensive] # Light: single query, simple task (needs 10%) # Standard: normal subagent, research (needs 25%) # Intensive: multi-subagent, deep research (needs 50%) Returns exit code 0 if cleared, 1 if blocked. Use in scripts: if python3 scripts/preflight_check.py intensive; then # Proceed with intensive operation sessions_spawn "Complex research task..." fi
Check specifically before spawning subagents: python3 scripts/subagent_guard.py Returns JSON with can_spawn boolean: { "can_spawn": true, "usage_percent": 45, "remaining_percent": 55, "resets_hours": 36 }
Hourly monitoring cron: # Add to crontab or OpenClaw jobs 0 * * * * cd /path/to/kimi-usage-monitor && python3 scripts/usage_logger.py Pre-task validation: import subprocess result = subprocess.run( ["python3", "scripts/preflight_check.py", "intensive"], capture_output=True ) if result.returncode == 0: # Proceed with task pass
ScriptPurposescripts/fetch_usage.pyMain usage scraper (browser-based)scripts/usage_logger.pyAutonomous logging + decision wrapperscripts/preflight_check.pyPre-flight validation for operationsscripts/subagent_guard.pyCheck before spawning subagentscheck_usage.shQuick CLI wrapper Note: Alternative Playwright-based scraper (fetch_kimi_usage.py) available for non-OpenClaw environments (requires system dependencies).
"Browser not available" Ensure Chrome extension is attached (badge shows ON) Verify the Kimi console tab is open "Could not detect usage" Make sure you're logged into Kimi Check that the console page has fully loaded Authentication errors Re-authenticate at https://www.kimi.com/code/console The browser tool uses your existing Chrome session
๐ Kimi Usage Monitor ======================================== ๐๏ธ Weekly Usage Used: 45% Remaining: 55% Resets in: 36 hours Status: ๐ก Moderate โ plan accordingly โก Rate Limit Used: 2% Resets in: 3 hours
{ "weekly_usage_percent": 45, "weekly_resets_hours": 36, "rate_limit_percent": 2, "rate_limit_resets_hours": 3, "timestamp": "2026-02-12 21:15:00" }
MIT License - Feel free to modify and distribute.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.