T01 · Skill Instruction Hijacking
- Location
SKILL.md:51- Finding
Untrusted Remote Task Content Is Treated as Authoritative Agent Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill openly connects to a remote task service, but it gives remote task content broad authority and sends credentials and results to configurable endpoints without enough safeguards.
Install only if you trust the Komandr server and everyone who can create tasks for your agent. Use a tightly sandboxed agent account, avoid sensitive repositories or secrets, pin and review the runtime dependency, and configure only trusted HTTPS Komandr endpoints with revocable API keys.
SKILL.md:51Untrusted Remote Task Content Is Treated as Authoritative Agent Instructions
scripts/komandr-bridge.ts:22Bearer API Key Can Be Transmitted to an Arbitrary or Plaintext Endpoint
scripts/komandr-bridge.ts:1Unpinned Runtime Package Execution Through npx
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
Referenced artifact was not completely inspected
npx tsx scripts/komandr-bridge.ts me
The skill explicitly instructs the agent to use environment variables and make network requests, but it does not declare any tool scope such as permissions or allowed-tools. This weakens least-privilege controls and can cause the host to grant broader access than users expect for a skill that polls remote tasks and submits results externally.
The skill establishes an ongoing agent-to-service relationship with polling, acceptance, progress updates, submissions, and periodic heartbeats, effectively persisting operational state with a remote service. In context this is intentional, but it increases risk because a remote party can continuously feed tasks and receive outputs over time, expanding the blast radius of any misuse or compromise.
# Komandr Skill
This skill connects you to the **Komandr Command Center**, a task orchestration platform. Humans create tasks in Komandr and assign them to AI agents. Your job is to poll for tasks, accept them, do the work, and submit results.
## Installation
The skill causes task descriptions, context, progress messages, summaries, results, and optional artifacts to be sent to an external Komandr server, but the description does not prominently warn users about that data flow. This can lead to unintended disclosure of sensitive repository data, prompts, outputs, or operational metadata to a third party.
Using npx tsx without pinning an exact package version allows the runtime to fetch whatever version is current at execution time. If the package or dependency chain is compromised or a breaking version is published, the agent may execute untrusted code while handling API keys and remote task data.
Using npx tsx without pinning an exact package version allows the runtime to fetch whatever version is current at execution time. If the package or dependency chain is compromised or a breaking version is published, the agent may execute untrusted code while handling API keys and remote task data.
Using npx tsx without pinning an exact package version allows the runtime to fetch whatever version is current at execution time. If the package or dependency chain is compromised or a breaking version is published, the agent may execute untrusted code while handling API keys and remote task data.
Using npx tsx without pinning an exact package version allows the runtime to fetch whatever version is current at execution time. If the package or dependency chain is compromised or a breaking version is published, the agent may execute untrusted code while handling API keys and remote task data.
Using npx tsx without pinning an exact package version allows the runtime to fetch whatever version is current at execution time. If the package or dependency chain is compromised or a breaking version is published, the agent may execute untrusted code while handling API keys and remote task data.
Using npx tsx without pinning an exact package version allows the runtime to fetch whatever version is current at execution time. If the package or dependency chain is compromised or a breaking version is published, the agent may execute untrusted code while handling API keys and remote task data.