OEE AI Cost Tracker
PassAudited by ClawScan on May 1, 2026.
Overview
This appears to be a simple local AI cost tracker; the main things to notice are that it stores usage metadata locally and expects Python even though the registry does not declare it.
This skill looks safe for its stated purpose. Before installing, make sure you are comfortable with a local usage.jsonl file being created in the skill directory, avoid logging sensitive descriptions, and confirm Python 3.10+ is available if you plan to run the scripts.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The skill may not work unless Python is already available, and the platform metadata may not warn you about that before use.
The skill documents a Python runtime requirement, while the registry metadata lists no required binaries and no install spec. This is an under-declared setup requirement, not evidence of hidden installation or remote code.
- Python 3.10+ (stdlib only)
The publisher should declare Python 3.10+ in metadata. Users should run only the bundled scripts they intend to use.
If descriptions contain project names, prompts, customer details, or other sensitive context, that information will remain in the local usage log.
The tracker persists user-supplied usage metadata, including descriptions and source labels, to a local usage.jsonl file.
"description": description, "source": source ... with open(_USAGE_PATH, "a") as f: f.write(json.dumps(entry) + "\n")
Keep log descriptions non-sensitive, protect or periodically delete usage.jsonl, and do not log secrets, prompts, or private customer data.