Security audit
Security checks across malware telemetry and agentic risk
This is a clearly described scheduler skill whose cron and systemd persistence are expected for its purpose, though users should review and remove scheduled jobs when done.
Install only if you intentionally want recurring automated Pilot tasks. Before running the examples, review the exact crontab or systemd entry, target script, log path, and Pilot peer; keep removal commands handy for deleting the cron entry or disabling the timer later.
**Add cron job:**
```bash
crontab -l | { cat; echo "0 * * * * /path/to/submit-task.sh"; } | crontab - # Every hour
crontab -l | { cat; echo "0 2 * * * /path/to/daily-backup.sh"; } | crontab - # Daily at 2 AM
```**Add cron job:**
```bash
crontab -l | { cat; echo "0 * * * * /path/to/submit-task.sh"; } | crontab - # Every hour
crontab -l | { cat; echo "0 2 * * * /path/to/daily-backup.sh"; } | crontab - # Daily at 2 AM
```
**Systemd timer (more reliable):**chmod +x "$SCRIPT_DIR/health-check.sh" # Install cron jobs crontab -l 2>/dev/null | grep -v 'pilot-cron' > /tmp/crontab.tmp || true cat >> /tmp/crontab.tmp <<EOF # pilot-cron: Health check every 5 minutes */5 * * * * $SCRIPT_DIR/health-check.sh >> $HOME/.pilot/logs/health-check.log 2>&1
Persistent=true EOF systemctl --user enable pilot-task.timer systemctl --user start pilot-task.timer ```
60/60 vendors flagged this skill as clean.
No suspicious patterns detected.