T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Third-Party Dependencies and Repository Code Are Installed and Executed
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to be an agent-orchestration helper, but it asks users to run mutable external code that controls Claude sessions, stores context, and uses external integrations without enough disclosure.
Review before installing. Run the orchestrator only from a pinned, audited commit or release, use a dedicated low-privilege environment, provide a least-privilege Notion token, keep the HTTP API bound to localhost with access controls, and avoid sending secrets or proprietary code unless you understand what is persisted and what is synced to Notion or Telegram.
SKILL.md:16Unpinned Third-Party Dependencies and Repository Code Are Installed and Executed
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
git clone https://github.com/TheAgentAcademy/agent-relay-orchestrator.git cd agent-relay-orchestrator npm install cp .env.example .env
npm start
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
git clone https://github.com/TheAgentAcademy/agent-relay-orchestrator.git cd agent-relay-orchestrator npm install cp .env.example .env
npm start
The metadata and setup require Notion credentials and describe visibility through an external service, but the skill does not warn that user prompts, worker outputs, or metadata may be transmitted to Notion or other third-party integrations. In this context, the omission is security-relevant because users may assume orchestration is local-only while sensitive agent data is actually shared externally.
The skill documents local HTTP endpoints that expose worker state, events, sessions, and metadata, and also describes persistence and auto-resume, but it does not warn users that sensitive prompts, outputs, and operational metadata may be retrievable through those endpoints or retained across restarts. In an agent orchestration context, these records can contain proprietary code, secrets, or system instructions, so omission of this warning meaningfully increases the risk of unintended disclosure.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl http://localhost:3890/health
Returns service status, active workers, and ticker state.
The manifest and top-level documentation consistently position the skill around Claude Code orchestration with Notion visibility, but the documented API section exposes a "Toggle Telegram Ticker" capability instead. This is not merely omitted detail: it names and documents a different integration target than the stated Notion visibility purpose, creating an active intent/documentation contradiction.