Agent Budget Controller

This skill appears to implement a local per-agent budget tracker as advertised, but check two things before installing: 1) Manifest vs docs: SKILL.md lists 'uv' as a required binary while INSTALL.md treats 'uv' as an optional installer tool. You only need python3 to run the CLI; 'uv' shouldn't be mandated at runtime. If you don't use 'uv', you can run scripts directly with python3. 2) Data egress in examples: Several examples/cron lines show piping budget reports to external message channels (Telegram, email, OpenClaw message send). The skill itself stores data locally, but those integration examples will transmit usage/cost data outside your machine. Only enable such integrations if you trust the destination and tooling. 3) Enforcement expectations: The docs are inconsistent about 'blocking' at 100% — the code and README indicate budget.check returns an exit code but does not automatically prevent LLM calls; you must wrap agent invocation (pre-call hook) to enforce blocks. If you need automatic enforcement, implement a wrapper that calls `budget check` and aborts when exit code != 0. 4) Quick checks to run locally before trusting it: inspect scripts/budget.py for subprocess or network usage, run the included tests (python3 tests/test_budget.py), and verify the files are written only under ~/.openclaw/budget/. If you want stricter privacy, avoid setting up cron/heartbeat lines that forward reports off-host. Given these inconsistencies (manifest requirement for 'uv' and the presence of external-report examples plus mismatched enforcement claims), treat the skill as suspicious until you confirm the installer/CI/integration steps you plan to use and audit the CLI script for any unexpected network calls.