T06 · System Persistence
- Location
job-monitor/SKILL.md:103- Finding
Persistent Daily Agent Execution Through launchd or Cron
- Content
View full analysis
Label com.jobsclaw.monitor ProgramArguments /bin/bash MONITOR_SCRIPT_PATH StartCalendarInterval Hour 9 Minute 0 StandardOutPath /tmp/jobsclaw-monitor.log StandardErrorPath /tmp/jobsclaw-monitor.err ``` ```bash launchctl load ~/Library/LaunchAgents/com.jobsclaw.monitor.plist ``` ```bash crontab -e # Add: run every day at 9:00 0 9 * * * /bin/bash MONITOR_SCRIPT_PATH ``` ### Technical Analysis The Skill instructs the Agent to create a shell script and register it as either a macOS LaunchAgent or a Linux cron job. This causes the script—and, indirectly, `claude -p` and the external UPCV MCP service—to execute across sessions without requiring the user to start another interactive Skill run. Scheduled execution is relevant to the declared daily-monitoring feature, but invoking a general-purpose AI Agent on a recurring basis is broader than the minimum privilege needed to perform a fixed job query. The referenced script remains mutable after scheduler registration, so any later modification to that script changes the behavior of every future scheduled execution. The workflow describes teardown commands, but it does not require an explicit approval step immediately before writing and loading the persistent scheduler configuration. It also d ...[truncated 1354 chars]- Remediation
View remediation
