T09 · Insecure Skill Coding Practices
- Location
SKILL.md:35- Finding
JWT Credentials and Sensitive Farm Data Transmitted Over Plaintext HTTP
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its farm-observation purpose, but it directs agents to send manager tokens, reports, and photos over unencrypted HTTP.
Review this skill carefully before installing. It should only be used on a trusted network or after the backend supports HTTPS, and users should require explicit confirmation before creating observations, tasks, maintenance entries, alerts, or photo uploads.
SKILL.md:35JWT Credentials and Sensitive Farm Data Transmitted Over Plaintext HTTP
The trigger phrases and activation criteria are broad enough that ordinary conversation in shared channels could be interpreted as an instruction to engage the skill and potentially prepare or initiate writes. In this skill context, broad auto-detection is more dangerous because the skill can create authenticated observation records and branch into related operational workflows, increasing the chance of unauthorized or unintended actions from ambiguous chat.
The 'What this does NOT handle' section says equipment maintenance scheduling or fleet status belongs to another skill. Yet later sections direct the agent to offer maintenance-related actions, log equipment issues against maintenance records, and cross-reference equipment maintenance history, which conflicts with the claimed scope boundary.
This is an active contradiction within the documentation itself. One section excludes maintenance scheduling and fleet-status handling, while later sections direct behavior that touches maintenance records and equipment availability, creating clear intent-code-style divergence in the skill instructions.
The manifest describes a skill for querying and creating field observations and AI-processed captures. However, the documented behavior instructs the agent to check other modules, correlate patterns, inspect equipment availability and maintenance history, and use weather/task context to drive recommendations, which materially broadens the skill from observation logging/querying into multi-system operational analysis.
No suspicious patterns detected.