cron-schedule
Pass
Audited by Gen Agent Trust Hub on May 11, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill utilizes CronCreate, CronList, and CronDelete tools to manage background workers that persist across session restarts. This behavior is consistent with the skill's stated purpose of scheduling maintenance and monitoring tasks.\n- [PROMPT_INJECTION]: The CronCreate tool accepts a
promptparameter to define worker behavior, which constitutes an indirect prompt injection surface where instructions are stored and executed asynchronously.\n - Ingestion points: The
promptargument in the CronCreate tool calls in SKILL.md.\n - Boundary markers: Not present in the provided examples.\n
- Capability inventory: Background workers have access to the
mcp__claude-flow__hooks_worker-dispatchtool.\n - Sanitization: The documentation does not specify sanitization or delimiting procedures for the prompt strings.
Audit Metadata