T06 · System Persistence
- Location
SKILL.md:117- Finding
Optional Cron Configuration Creates Persistent Scheduled Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is purpose-aligned analytics, but it broadly records sensitive usage details across sessions and includes unsafe logging and optional persistence patterns that need review.
Install only if you intentionally want cross-session local analytics for skill usage. Treat the log as sensitive: avoid raw trigger phrases, redact group or personal details, use a safe JSON-writing helper instead of echo substitution, set restrictive file permissions, define retention, and skip the optional cron entry unless the referenced script is audited and easy to remove.
SKILL.md:117Optional Cron Configuration Creates Persistent Scheduled Execution
SKILL.md:37Untrusted Analytics Metadata Is Interpolated into a Shell Command
SKILL.md:24Cross-Session Behavioral Metadata Is Stored in Plaintext Without Defined Protections
The skill is designed to record every invocation along with trigger phrases and context across all sessions, but it provides no user-facing notice, consent flow, or minimization guidance. Even though the data stays local, these fields can contain sensitive behavioral and conversational metadata, creating a privacy risk if the file or generated reports are accessed by others.
The log format stores user-provided trigger phrases in plaintext and later uses them in reports, which can directly expose private requests, names, internal topics, or other sensitive content. Because triggers are free-form, the skill may capture far more sensitive material than intended, and anyone with access to the log or report can read it.
The instructions tell agents to log real trigger and context values before doing any work, making retention of potentially sensitive user content and conversation metadata a default behavior. This increases risk because collection happens automatically and broadly, including in direct messages or named groups where metadata itself may be sensitive.
The report output intentionally displays recent trigger phrases, which can reveal private user requests to anyone who views the analytics summary. This amplifies the privacy risk beyond storage alone by republishing sensitive content in a human-readable format that may be shared more widely than the raw log.
The reset/archive procedure moves the active log and starts a fresh file without warning operators that they are altering operational history and potentially disrupting audit continuity. This is primarily an integrity and operational transparency issue rather than a direct exploit path, but it can still hinder investigations or usage reviews.