T06 · System Persistence
- Location
SKILL.md:228- Finding
Persistent Weekly Processing Through a Scheduled Cron Job
- Content
View full analysis
" }, "sessionTarget": "isolated", "wakeMode": "now", "payload": { "kind": "agentTurn", "message": "Run biz-relationship-pulse. Read {baseDir}/config.md, {baseDir}/pipeline.md, and {baseDir}/context.md. Scan connected sources (Gmail, LinkedIn, WhatsApp) for stalled commercial conversations. Score each candidate. Surface top 3-5 scoring 8+ (or 6+ if fewer qualify). For each: write a relationship brief and one specific re-opening message. Update pipeline.md. Deliver via configured channel.", "lightContext": true }, "delivery": { "mode": "announce", "channel": "", "to": "", "bestEffort": true } } ``` ``` ### Technical Analysis The setup directs the Agent to register a scheduled task that survives the initiating session and executes every Monday. Each execution reads persistent local state, accesses connected communication services, updates the stored pipeline, and delivers a report. Scheduled execution is part of the declared weekly relationship-monitoring function, but the instructions do not require a separate informed-consent checkpoint immediately before registration. They also do not document how the user can inspect, pause, or remove the scheduled task. This creates persistent access whose lifetime may exceed the user's immediate intent. ### Attack Path 1. The user invokes the Skill and completes initial setup. 2. The Agent follows ...[truncated 1109 chars]- Remediation
View remediation
