T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned and Unauditable Executable PyPI Dependency
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This nutrition tracking skill is useful and mostly purpose-aligned, but it stores sensitive diet and health information silently and installs persistent prompts without clear consent.
Install only if you are comfortable with the agent keeping long-term nutrition, allergy, diet, and health-context notes and with a heartbeat integration that can prompt you in later sessions. Review or remove the heartbeat block if you do not want proactive prompts, and prefer a pinned, reviewed nutrition-cli package before relying on it.
SKILL.md:14Unpinned and Unauditable Executable PyPI Dependency
ONBOARDING.md:52Mandatory Persistent Heartbeat Hook Installed Before Reminder Consent
SKILL.md:49Shell Command Injection Through Unescaped User-Controlled Values
SKILL.md:100Silent Persistent Collection of Sensitive Health and Behavioral Data
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
## Nutrition profile
<!-- nutrition-cli managed section — do not edit manually -->
- Daily calorie target: {KCAL_TARGET} kcal
- Protein goal: {PROTEIN_G}g/day
- Fat limit: {FAT_G}g/day (optional)
The trigger conditions are intentionally broad enough to activate on casual mentions of food in ordinary conversation. That makes unintended invocation likely and increases the chance the skill will collect, suggest logging, or persist sensitive dietary information when the user did not actually ask for nutrition tracking.
The meal-logging section reinforces ambiguous activation by treating essentially any food mention in passing as a trigger. In context, this is especially dangerous because later steps can lead to nutrition searches, offers to log, and persistent memory updates, turning casual conversation into data collection and profiling.
The skill explicitly instructs silent writes of sensitive health context, food preferences, calorie patterns, and behavior observations to persistent memory without user-facing warning in the skill description. This is a strong privacy and consent failure because users may believe they are getting one-off nutrition help while the system is quietly building a sensitive profile.
The skill behavior includes checking daily memory files and noting incidental food mentions, but the snippet provides no user-facing warning that these statements may be stored or used for meal tracking. In a nutrition context this is more sensitive than ordinary preferences because it can reveal health, dieting, religious, or medical information, so silent collection increases privacy harm.
The snippet explicitly instructs the agent to react to any incidental mention of food and to note it before asking whether it should be logged. That creates a privacy and consent risk because casual conversation can be transformed into health- or diet-related tracking without a clear opt-in boundary, and nutrition data can be sensitive personal information.
The onboarding flow instructs the agent to collect sensitive health-related information, including calorie targets, protein goals, dietary restrictions, allergies, and meal timing, and persist it to MEMORY.md without requiring explicit user consent or clearly warning that the data will be stored long-term. In a nutrition skill, this data is especially sensitive because it can reveal health status, religious practices, disabilities, or medical risks, and persistent storage increases exposure to later unintended access or reuse.
The skill silently writes long-term health-related data, food preferences, behavior patterns, and inferred trends into persistent memory. Even if intended to improve personalization, this collects sensitive personal and health-adjacent information without prominent upfront disclosure or explicit consent, creating privacy, profiling, and retention risks well beyond a simple nutrition lookup tool.
The skill creates persistent cron jobs that can trigger future agent actions outside the immediate user request. Although reminder functionality is plausibly related to nutrition tracking, scheduled execution increases the skill's authority and persistence, and the embedded scheduled prompts can cause ongoing data collection or logging if enabled. This is riskier because the skill can continue acting later in a separate session context.
No suspicious patterns detected.