Back to skill

Security audit

Conversation Flow Monitor

Security checks for vulnerabilities and agentic risk

Overview

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.

Vulnerability Patterns
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (3)

T08 · Insecure Dependencies

Warning
Location
README.md:59
Finding

Unpinned Third-Party Installer Execution

Content
View full analysis
Remediation
View remediation

T02 · Agent Memory Poisoning

Warning
Location
SKILL.md:77
Finding

Unsafe Promotion of Recovery Content into Persistent Agent State

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/conversation_monitor.py:140
Finding

Timeout Wrappers Do Not Reliably Terminate Underlying Operations

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Findings (14)

Rp1

Medium
Category
MCP Rug Pull
Confidence
90% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
90% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Low
Category
Not specified by scanner
Confidence
76% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
91% confidence
Finding

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.

Content

Scanner excerpt · package.json (reported line 23)May include surrounding context.

json
},
  "dependencies": {},
  "devDependencies": {
    "flake8": "^3.9.2"
  }
}