T01 · Skill Instruction Hijacking
- Location
SKILL.md:16- Finding
Mandatory External Completion Gate Hijacks Agent Workflow
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed APort completion-check workflow, but it sends task details to an external service and gives that service control over whether the agent may call work complete.
Install only if you intentionally want APort to act as a remote completion gate. Do not use it on confidential code, customer data, regulated work, or secrets unless your organization has approved APort as a third-party processor and you know exactly which fields will be sent. Prefer a pinned, verified setup method over the unpinned `npx` command.
SKILL.md:16Mandatory External Completion Gate Hijacks Agent Workflow
SKILL.md:41Potential Disclosure of Full Task Output and Metadata to an External Service
SKILL.md:31Unpinned Third-Party Package Execution Through npx
SKILL.md:31Agent Is Directed to Follow Mutable Remote Instructions
The skill directs agents to run npx aport-id without pinning a version or integrity-verified package source. That creates a supply-chain risk: a future malicious or compromised package version could be executed automatically in a privileged agent environment.
The skill explicitly instructs agents to include output_content and send it to a remote verification API when scanning is enabled, but it provides no consent gate, redaction guidance, or user-facing warning. In an agent context, this can exfiltrate proprietary code, sensitive documents, secrets, or regulated data to a third party during normal task completion flow.
Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.
- `oap.criteria_not_met` → attempt to resolve the criterion, then retry
Maximum retries: 3. After 3 denials on the same task, surface the issue to the user.
Do not loop indefinitely.
## Links
This is the same unpinned npx aport-id reference repeated in the links section, so it carries the same supply-chain execution risk. Repetition increases the chance an agent or operator will follow the unsafe invocation path.
No suspicious patterns detected.