Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Track and control token consumption across OpenClaw cron jobs
Track and control token consumption across OpenClaw cron jobs
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.
Track and control token consumption across OpenClaw cron jobs, fallback chains, and sessions.
openclaw skills install aviclaw/token-budget-monitor
# Check current usage node track-usage.js status # Check budget for a specific job node track-usage.js check daily-tweet # Alert if over budget node track-usage.js alert # Get model recommendations node track-usage.js recommend
Add to cron jobs to track usage: // After LLM call completes const usage = result.usage; exec('node /path/to/track-usage.js track <job-name> ' + usage.input_tokens + ' ' + usage.output_tokens + ' ' + model);
Edit config.json: { "dailyLimit": 100000, "jobLimits": { "daily-tweet": 5000, "rss-brief": 15000 }, "alertThreshold": 0.8, "freeModels": [ "nvidia/moonshotai/kimi-k2.5", "google/gemini-2.0-flash-exp" ] }
Per-job token tracking Daily budget limits Per-job custom limits Alert when threshold exceeded Recommend free model alternatives
GitHub: @aviclaw
MIT
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.