Back to skill

Security audit

Cron Retry

Security checks for vulnerabilities and agentic risk

Overview

This skill is coherent, but it asks agents to automatically rerun failed cron jobs without enough safeguards against repeated or duplicate side effects.

Install only for cron jobs that are known to be idempotent or have duplicate-suppression protections. Before adding the heartbeat integration, add explicit per-job opt-in, a cooldown using lastRunAtMs, retry limits, logging, and manual review for repeated failures.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:72
Finding

Unbounded Retries Can Cause Repeated or Duplicate Cron Job Execution

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill instructs agents to automatically rerun failed cron jobs based on error text without warning that reruns may repeat side effects such as duplicate messages, duplicate API writes, or repeated external actions. Because cron jobs can be non-idempotent, automatic recovery in this context increases the chance of unintended duplicate operations after transient failures.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill claims it prevents retry loops by checking lastRunAtMs, but the provided implementation never performs that check before rerunning failed jobs. In an automatic heartbeat-driven workflow, this discrepancy can cause repeated re-execution of the same failing cron job, especially during prolonged outages or recurring transient errors, leading to duplicate actions and unnecessary load.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.