Token Usage Tracker

Token usage logging, alerting, and context-compression utilities for OpenClaw. Use when you want to track per-call token usage, normalize timestamps, and red...

This skill appears to do exactly what it says: local token accounting, timestamp conversion, simple summarization, and example alerting. Before installing or deploying: 1) Read the scripts (they are small) and choose a safe log_folder (not a world-readable or system directory). 2) Restrict filesystem permissions for the log folder and consider rotating/retention to avoid unbounded disk growth. 3) Audit what you log — call payloads may include sensitive data; add redaction or avoid logging full contexts if privacy is a concern. 4) Do not enable or add webhook/web network calls (token_alerts hints at this) unless you trust the endpoint and sanitize data. 5) If you deploy the systemd example, update ExecStart path and User from the sample values before enabling. 6) Test in a controlled environment first. Overall: coherent and low-risk if used as-local examples and properly configured.

Type: OpenClaw Skill Name: oken-usage-tracker Version: 1.0.0 The skill bundle provides utilities for token usage logging, alerting, and context compression, aligning perfectly with its stated purpose. All scripts perform local file I/O within a designated log folder and read a local configuration file. There is no evidence of data exfiltration, malicious execution, or unauthorized persistence. The `README.md` contains a prompt for the AI agent to 'package' the skill, but this is a benign meta-instruction related to skill management, not a malicious prompt injection attempt.