T08 · Insecure Dependencies
- Location
README.md:59- Finding
Unpinned Third-Party Installer Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a plausible reliability-monitoring skill, but it expands into persistent agent-memory changes and automatic log maintenance without enough scoping or user control.
Review this skill carefully before installing. Its basic monitoring code is not an exfiltration tool, but you should avoid enabling automatic memory promotion, AGENTS.md/SOUL.md/TOOLS.md edits, or heartbeat log cleanup unless you can inspect and approve each change. Prefer an immutable, verified install source instead of the placeholder unpinned npx/GitHub commands, and configure logging retention/redaction before using it on sensitive conversations or workspaces.
README.md:59Unpinned Third-Party Installer Execution
SKILL.md:77Unsafe Promotion of Recovery Content into Persistent Agent State
scripts/conversation_monitor.py:140Timeout Wrappers Do Not Reliably Terminate Underlying Operations
The README instructs users to run npx skills add ... without pinning a specific package version. Because npx resolves and executes packages dynamically, a future malicious or compromised release of the referenced package or its dependencies could execute arbitrary code on the user's system during installation. In a setup/install context, this is more dangerous because users are likely to run the command verbatim with local privileges.
The README describes persistent logging of conversation flow issues, diagnostics, and learnings to local files such as log directories and .learnings/* without clearly warning users that potentially sensitive prompts, outputs, file paths, or operational metadata may be retained. This creates a privacy and data-handling risk, especially for an agent-monitoring skill whose normal function involves observing and recording conversation behavior over time.
The skill describes file-validation behavior and references reading skill files, but it does not declare any explicit tool scope such as permissions or allowed-tools. That mismatch can cause the agent to exercise file access implicitly or unexpectedly, weakening least-privilege controls and making review of actual capabilities harder.
The skill claims to monitor conversation flow, but these sections expand its role into modifying persistent memory and workspace governance files like SOUL.md and TOOLS.md. That scope drift is dangerous because a monitoring skill can become a persistence or policy-modification mechanism, enabling unintended long-term influence over agent behavior.
The recovery table includes auto-fixing skill files and creating missing directories/files, which goes beyond monitoring into autonomous mutation of files and execution context. Automatic repair actions can be abused or can unintentionally alter trusted artifacts, especially when the skill has vague activation boundaries and no explicit write constraints.
The installation/availability language implies broad automatic applicability, but the skill does not define concrete trigger conditions, boundaries, or exclusions. Ambiguous activation increases the chance that it runs during unrelated tasks and applies monitoring, retries, file checks, or recovery logic in contexts where those actions are inappropriate or risky.
The documented heartbeat behavior extends beyond conversation-flow monitoring into file maintenance and integrity-checking, which broadens the operational scope of the skill. Scope creep of this kind is risky because users may grant trust or deployment approval based on the manifest description without realizing the skill can perform filesystem-affecting actions.
Automatic log cleanup implies deletion of local data, yet the examples do not clearly warn about deletion scope, retention consequences, or recovery limitations. In an agent skill context, undocumented data modification or deletion can cause loss of forensic logs, troubleshooting information, or user data if paths are misconfigured.
The document downplays the skill as containing only core monitoring functionality while elsewhere describing autonomous heartbeat actions such as log cleanup and integrity validation. That mismatch can mislead operators about the skill's effective scope and permissions, increasing the chance that maintenance or integrity-related actions run without proper review.
On timeout and exception paths, the code logs stringified args and kwargs into an in-memory error log, which can capture secrets, prompts, file paths, tokens, or user content without redaction. In this skill context, tool wrappers are likely to handle sensitive conversation and operational data, so failures could inadvertently retain or expose that data through logs, summaries, or downstream debugging output.
The decorator advertises configurable timeout protection but never passes the provided timeout value into execute_with_timeout/execute_with_retry, so callers may believe long-running or hung tool calls are bounded when they are not. In a conversation-flow monitoring skill, that undermines the core reliability and safety guarantee and can allow denial-of-service style stalls or resource exhaustion from unexpectedly long operations.
The markdown shows browser navigation and later recommends monitoring external API and network operations, which may send user or system data over the network. The document does not include any warning reminding users to avoid sending sensitive data or to verify destinations before use.
Validating skill file integrity is a separate capability from handling stuck conversations, timeouts, and recovery for agent interactions. While it may be operationally useful, this file-level integrity checking is not an obvious or direct requirement of a conversation-flow monitor based on the manifest description alone.
The devDependency uses a caret range (^3.9.2), which allows newer compatible versions to be installed. This can introduce build-time supply chain risk if a later allowed release is compromised or behaves unexpectedly, even though it does not directly affect runtime behavior of the skill.
},
"dependencies": {},
"devDependencies": {
"flake8": "^3.9.2"
}
}