Hermes Cron Job Audit — May 26 2026
Audit time: 2026-05-26 12:11 UTC
Total cron entries: 42
Hermes-related: 42
All Cron Entries
| Schedule | Command |
|---|---|
| 30 0 * * * | /usr/bin/python3 /home/us/.hermes/scripts/cleanup_stale_state.py >> /home/us/.hermes/logs/state-cleanup.log 2>&1 |
| 0 8 * * * | /home/us/.hermes/scripts/spam-scanner.py >> /home/us/.hermes/logs/spam-scanner-08.log 2>&1 |
| 0 14 * * * | /home/us/.hermes/scripts/spam-scanner.py >> /home/us/.hermes/logs/spam-scanner-14.log 2>&1 |
| 0 18 * * * | /home/us/.hermes/scripts/spam-scanner.py >> /home/us/.hermes/logs/spam-scanner-18.log 2>&1 |
| 0 2 * * * | /home/us/.hermes/scripts/masterdash-backup.sh >> /home/us/.hermes/logs/masterdash-backup.log 2>&1 |
| 15 2 * * * | /home/us/.hermes/scripts/datagate-db-backup.sh >> /tmp/db_backup_cron.log 2>&1 |
| 0 4 * * 0 | /usr/bin/python3 /home/us/.hermes/scripts/content-audit.py > /home/us/.hermes/reports/content-audit-$(date +%Y%m%d).j |
| 15 4 * * 0 | /usr/bin/python3 /home/us/.hermes/scripts/backup_verify.py –test-restore >> /home/us/.hermes/logs/backup-verify.log 2>& |
| */5 * * * * | /home/us/.hermes/scripts/uptime-monitor.sh >> /dev/null 2>&1 |
| 0 9 1-7 * 1 | /home/us/.hermes/scripts/health-check.sh –json > /home/us/.hermes/reports/security-review-$(date +%Y-%m-%d).json 2>& |
| 0 10 * * 1 | /home/us/.hermes/scripts/wp-update-tracker.py >> /home/us/.hermes/logs/wp-update-tracker.log 2>&1 |
| 0 6 * * 1 | /home/us/.hermes/scripts/run-weekly-reports.sh |
| 0 3 * * 0 | /usr/bin/python3 /home/us/.hermes/scripts/weekly_self_improvement_review.py >> /home/us/.hermes/logs/weekly-review.log 2 |
| 0 7 * * * | /usr/bin/python3 /home/us/.hermes/scripts/log_analyzer.py –hours 24 –output /home/us/.hermes/reports/log-analysis-$(da |
| 0 */6 * * * | /usr/bin/python3 /home/us/.hermes/scripts/resource_monitor.py –json > /home/us/.hermes/reports/resource-$(date +%Y%m |
| 0 9 * * * | /usr/bin/python3 /home/us/.hermes/scripts/ssl_expiry_monitor.py –json > /home/us/.hermes/reports/ssl-$(date +%Y%m%d) |
| 0 5 * * 1 | /usr/bin/python3 /home/us/.hermes/scripts/vuln_scanner.py –output /home/us/.hermes/reports/vuln-scan-$(date +%Y%m%d) |
| 0 1 * * * | /usr/bin/python3 /home/us/.hermes/scripts/log_rotation.py >> /home/us/.hermes/logs/log-rotation.log 2>&1 |
| 0 3 * * * | /usr/bin/python3 /home/us/.hermes/scripts/cron_recovery.py >> /home/us/.hermes/logs/cron-recovery.log 2>&1 |
| 0 10 * * 6 | /usr/bin/python3 /home/us/.hermes/scripts/update_safety.py –check-only >> /home/us/.hermes/logs/update-safety.log 2>&1 |
| 0 6 * * 0 | cd /home/us/.hermes/scripts && /usr/bin/python3 regression_test_runner.py –report –save-baseline >> /home/us/.hermes/l |
| 0 5 * * 0 | /usr/bin/python3 /home/us/.hermes/scripts/pentest_scanner.py >> /home/us/.hermes/logs/pentest-scanner.log 2>&1 |
| 0 4 * * * | /usr/bin/python3 /home/us/.hermes/scripts/secrets_rotation_scheduler.py check >> /home/us/.hermes/logs/secrets-rotation. |
| 0 6 * * * | /usr/bin/python3 /home/us/.hermes/scripts/cve-monitor.py >> /home/us/.hermes/logs/cve-monitor.log 2>&1 |
| 30 6 * * * | /usr/bin/python3 /home/us/.hermes/scripts/dep-vuln-scanner.py >> /home/us/.hermes/logs/dep-vuln.log 2>&1 |
| 10 7 * * * | /usr/bin/python3 /home/us/.hermes/scripts/morning_briefing.py >> /home/us/.hermes/logs/morning-briefing.log 2>&1 |
| 20 7 * * * | /usr/bin/python3 /home/us/.hermes/scripts/trending-topic-scanner.py >> /home/us/.hermes/logs/trending-topics.log 2>&1 |
| 30 7 * * * | /usr/bin/python3 /home/us/.hermes/scripts/keyword-opportunity-finder.py >> /home/us/.hermes/logs/keyword-opps.log 2>&1 |
| 10 8 * * * | /usr/bin/python3 /home/us/.hermes/scripts/threat-digest-generator.py >> /home/us/.hermes/logs/threat-digest.log 2>&1 |
| 15 8 * * * | /usr/bin/python3 /home/us/.hermes/scripts/incident-checklist-generator.py >> /home/us/.hermes/logs/incident-checklist.lo |
| 30 8 * * * | /usr/bin/python3 /home/us/.hermes/scripts/content-brief-generator.py >> /home/us/.hermes/logs/content-briefs.log 2>&1 |
| 55 23 * * * | cd /home/us/.hermes/scripts && python3 daily_cost_summary.py –budget 5.0 –alert-threshold 80 >> /home/us/.hermes/logs/ |
| 0 9 * * 0 | /home/us/.hermes/scripts/weekly_health_trend_report.sh –output text –days 7 >> /home/us/.hermes/reports/health_trend_c |
| 30 5 * * * | cd /home/us/.hermes/scripts && python3 task_priority_scorer.py >> /home/us/.hermes/logs/task_priority_scorer.log 2>&1 |
| 15 6 * * * | cd /home/us/.hermes/scripts && python3 blocker_detector.py >> /home/us/.hermes/logs/blocker_detector.log 2>&1 |
| 0 11 * * 1 | /usr/bin/python3 /home/us/.hermes/scripts/weekly_seo_digest.py >> /home/us/.hermes/logs/weekly-seo-digest.log 2>&1 |
| 40 6 * * * | /home/us/.hermes/scripts/daily_health_check.sh >> /tmp/daily_health_check.log 2>&1 |
| 0 12 * * 1 | /tmp/newsletter_cron.sh |
| */5 * * * * | /home/us/.hermes/scripts/datagate-ping-checker.sh >> /tmp/ping_checker_cron.log 2>&1 |
| */15 * * * * | /usr/bin/python3 /home/us/.hermes/scripts/cron_failure_alert.py >> /home/us/.hermes/reports/cron-failure-alerts/alert_cr |
| 0 2 1 * * | /usr/bin/python3 /home/us/.hermes/scripts/monthly_skill_freshness.py >> /home/us/.hermes/logs/skill-freshness-review.log |
| 0 6 * * 1 | /usr/bin/python3 /home/us/.hermes/scripts/weekly_content_scan.py >> /home/us/.hermes/logs/weekly_scan.log 2>&1 |
Key Findings
- Total scheduled jobs: 42
- Hermes agent crons: 42
- Recommendation: Consolidate overlapping schedules to reduce server load
- Best practice: Stagger cron runs to avoid concurrent execution conflicts
Optimization Opportunities
- Jobs running at similar times should be staggered by 5-10 minutes
- Long-running jobs should have timeout guards
- Failed jobs should have automatic retry with exponential backoff
- Consider reducing frequency of low-priority jobs during off-peak hours