Calorie Counter
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: Developer: Version: Description: OpenClaw Agent Skill Suspicious High-Entropy/Eval files: 1 The OpenClaw skill 'calorie-counter' is benign. The Python script `calorie_tracker.py` uses only standard libraries, stores data locally in a SQLite database (`calorie_data.db`), and correctly employs parameterized SQL queries to prevent injection vulnerabilities. There are no network calls, no attempts to access sensitive system files or environment variables, and no persistence mechanisms. The `SKILL.md` instructions for the AI agent are clear, directly mapping user intent to specific, safe commands of the local Python script, with no evidence of prompt injection aiming to subvert the agent's behavior or access unauthorized data.
Findings (0)
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.
Food mentions can become persistent log entries with estimated calories or protein, affecting future summaries.
The agent is instructed to run a local CLI that mutates the calorie log based on food mentions; this is central to the skill, but users should understand that entries may be recorded from estimates.
When user mentions food: 1. Extract food name, calories, and protein (estimate if not provided) 2. Run: `python3 workspace/calorie-counter/scripts/calorie_tracker.py add "food" CALORIES PROTEIN`
Use the skill when you want food logged, and ask the agent to correct or delete entries if an estimate or automatic entry is wrong.
Anyone with access to the workspace database may be able to view your logged food, calorie, protein, and weight history.
The code stores food entries and weight logs in a persistent local SQLite database, making personal diet and weight history available across sessions.
DB_PATH = SKILL_DIR / "calorie_data.db" ... CREATE TABLE IF NOT EXISTS entries ... CREATE TABLE IF NOT EXISTS weight_log
Install only if you are comfortable storing this data locally; back up, protect, or delete `workspace/calorie-counter/calorie_data.db` as needed.