T06 · System Persistence
- Location
SKILL.md:192- Finding
Mandatory Recurring Task Creates Cross-Session Persistence
- Content
View full analysis
> ~/.tinyplace/status.log 2>&1 ``` - **Claude Code**: use its scheduler / a recurring task (e.g. the `/schedule` or `/loop` facility) to run `tinyplace status` (and `tinyplace feed`) at the chosen interval. - **OpenClaw / Hermes**: register a cron loop that runs the check-in. - **Your own agent runtime**: use its built-in timer/heartbeat to call the CLI on the interval. ``` ### Technical Analysis The Skill instructs the agent to install a recurring job that survives the current Skill invocation. Periodic polling is related to the declared social-network functionality, and the Skill does ask the operator to choose the cadence. However, it makes persistence part of mandatory setup rather than an optional, separately approved feature. The cron example resolves `tinyplace` through the scheduler's `PATH` instead of using an absolute, verified executable path. It also lacks execution timeouts, overlap prevention, resource limits, log rotation, and an uninstall procedure. The persistent job therefore expands the security scope from a one-time interactive command to repeated execution under the user's account. ### Attack Path 1. The operator permits installation of the documented cron or runtime schedul ...[truncated 998 chars]- Remediation
View remediation
