T06 · System Persistence
- Location
SKILL.md:102- Finding
Persistent Unattended Agent Execution Through a Nightly Scheduled Task
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is transparent about overnight automation, but it grants broad recurring access to conversations, memory, files, scripts, and messaging without enough scoping or review controls.
Install only if you are comfortable with an agent running every night without you present. Before enabling it, narrow the session and memory sources it may read, keep outputs local by default, require review before any external message, prohibit unattended script or alias creation, and add an explicit way to pause or remove the cron job.
SKILL.md:102Persistent Unattended Agent Execution Through a Nightly Scheduled Task
SKILL.md:106Broad Recurring Access to Private Session History and Persistent Memory
SKILL.md:51Unapproved Creation of Executable Scripts and Modification of Persistent Workspace State
This is a direct policy contradiction: the skill says external-facing actions are never allowed without permission, then instructs the agent to send a briefing via a configured messaging channel. In practice, agents often treat the operational step as authoritative, so this inconsistency can lead to unauthorized outbound messages containing sensitive context from scanned sessions or memory files.
The skill is explicitly designed to make autonomous workspace changes while the user sleeps, but the top-level description does not clearly warn that it may modify files, scripts, memory, or repository state. That omission increases the risk of users enabling the skill without understanding the breadth of autonomous changes, which can lead to unintended file edits, repo churn, or disruption of established workflows.
The skill states that external-facing actions are Tier 3 and require permission, yet its nightly workflow still includes sending a morning briefing through a messaging channel as part of routine execution. That creates an autonomous outbound communication path that may disclose session-derived or workspace-derived information without an explicit per-run approval, undermining the stated safety boundary.
The morning briefing is generated from session history and memory files, but the skill provides no privacy notice or data-minimization guidance before sending that content through a messaging channel. This creates a realistic risk of leaking sensitive conversation details, internal project information, or personal data into third-party messaging systems.
The example configuration fixes the timezone to 'America/Chicago', which imposes a locale-specific default without user opt-in. The policy allows locale constraints only when justified or optional, and neither is provided here.