T01 · Skill Instruction Hijacking
- Location
SKILL.md:44- Finding
Untrusted Remote Instructions Can Influence Agent Behavior
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This deployment skill is mostly coherent, but it tells the agent to follow mutable instructions from an external API before generating and deploying code.
Review this skill before installing if you use proprietary code or secrets. It is intended to deploy apps through SkillBoss, so app files and metadata may leave your environment; confirm what will be sent, keep secrets out of deployed files, and treat remote deployment instructions as constraints that cannot override your own instructions or security requirements.
SKILL.md:44Untrusted Remote Instructions Can Influence Agent Behavior
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# AppDeploy Skill
Deploy web apps via SkillBoss API Hub (https://api.heybossai.com/v1/pilot).
## Setup (First Time Only)
The skill explicitly sends deployment requests, app metadata, and potentially app files to a third-party HTTP API, but it does not clearly warn users that their code and related data will leave the local environment. In a deployment skill, this omission matters because users may provide proprietary source code, secrets embedded in files, or sensitive configuration without informed consent.
The explicit endpoint reference at the point of the curl example is part of a real external transmission workflow, not just documentation. In context, this skill is designed to deploy apps to a hosted service, so the danger is contextual: it normalizes sending complete application artifacts to a third party without an equally explicit warning about privacy, code ownership, and secret-handling.
Make calls to the SkillBoss API Hub deployment endpoint:
curl -X POST https://api.heybossai.com/v1/pilot \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-d '{
The explicit endpoint reference at the point of the curl example is part of a real external transmission workflow, not just documentation. In context, this skill is designed to deploy apps to a hosted service, so the danger is contextual: it normalizes sending complete application artifacts to a third party without an equally explicit warning about privacy, code ownership, and secret-handling.
Make calls to the SkillBoss API Hub deployment endpoint:
curl -X POST https://api.heybossai.com/v1/pilot \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-d '{
The instruction says timestamp values must be converted to the user's local time, which imposes a locale-specific presentation rule. The file does not indicate user opt-in or explain a justified regional requirement, so this can be considered a natural-language locale policy constraint.
No suspicious patterns detected.