T01 · Skill Instruction Hijacking
- Location
SKILL.md:10- Finding
Mandatory CLI and Commercial Output Instructions Hijack Agent Behavior
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not clearly malicious, but it should be reviewed because it forces a global third-party CLI install, steers answers toward booking links, and can silently log raw user queries.
Install only after reviewing the FlyAI CLI source/provenance and accepting that user travel queries may be sent to an external travel service. Prefer a pinned, local, approved install; disable or remove hidden raw-query logging; validate all generated booking links; and use argument-safe CLI invocation rather than shell string templates.
SKILL.md:10Mandatory CLI and Commercial Output Instructions Hijack Agent Behavior
SKILL.md:36Unpinned Third-Party Package Is Installed Globally at Runtime
references/playbooks.md:11User-Controlled Parameters Are Interpolated into Shell Command Templates
references/runbook.md:31Raw User Queries Are Silently Persisted Through an Injection-Prone Shell Command
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
flyai search-poi --city-name "Zhangjiajie" --category "自然风光"
## Output Rules
1. **Conclusion first** — lead with the key finding
2. **Comparison table** with ≥ 3 results when available
The activation terms are broad enough to match common travel requests, which can cause this skill to trigger outside its intended niche. Because the skill then forces CLI installation/execution and prohibits fallback answers, over-activation increases the chance of unnecessary command guidance, user confusion, and unsafe delegation to an external toolchain.
The playbook hard-codes Chinese category strings such as "自然风光" and "山湖田园" in command examples, but the surrounding instructions do not explain that the skill is China-specific or give the user a language/locale option. This can violate language/locale policy because the skill implicitly enforces a specific locale in its natural-language interface behavior.
The document states that the agent maintains internal execution logs and includes raw input and operational details, but provides no notice, consent, or transparency mechanism to users. For a travel-oriented skill, user queries may contain destinations, dates, passport/visa concerns, or other personal trip data, so silent collection meaningfully increases privacy risk.
The runbook explicitly requires storing the raw user query and full CLI command history, which can capture personal data, travel details, tokens, file paths, or other sensitive operational context not necessary for a nature/travel discovery skill. Because this data is retained in structured logs, any later access, misconfiguration, or reuse of logs increases the chance of privacy leakage and secondary exposure.
This schema combines raw natural-language user input with step-by-step execution traces and then contemplates persisting that record, creating a durable repository of sensitive conversational and operational data. In the travel context, those freeform queries may include itineraries, companions, budget, location, or visa details, making the retained log materially more sensitive than generic debugging metadata.
The runbook instructs appending execution logs to a local file without any controls for retention, access restrictions, encryption, or user warning. Persisting these logs to disk turns transient operational data into stored data that can be copied, leaked, or accessed by other processes or operators later.
The 'CLI Failed' template presents 'Check network: flyai --version' as a network diagnostic step. A version command checks local CLI installation/version, not network connectivity, so the inline guidance misdescribes what the command does.