Back to skill

Security audit

Cron Health Monitor

Security checks for vulnerabilities and agentic risk

Overview

The skill is a disclosed cron monitoring and repair playbook with no executable payloads, but users should keep control over any automatic cron changes.

Install only if you want an agent to help inspect and repair cron jobs. Before enabling automatic repair, confirm which cron jobs, output paths, alert channels, and update permissions the agent may use.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

Terms like 'cron health' and 'consecutive errors' are generic operational language and lack a clearly defined activation scope, making accidental invocation likely during normal troubleshooting conversations. Because the skill is designed to monitor, diagnose, and auto-delegate repairs, ambiguous triggers can lead to unintended access to cron state or unnecessary remediation workflows.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

Terms like 'cron health' and 'consecutive errors' are generic operational language and lack a clearly defined activation scope, making accidental invocation likely during normal troubleshooting conversations. Because the skill is designed to monitor, diagnose, and auto-delegate repairs, ambiguous triggers can lead to unintended access to cron state or unnecessary remediation workflows.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

After an English frontmatter summary, the substantive skill instructions are written entirely in Chinese and do not indicate that language selection is optional. This creates a language/locale policy issue because users are not given a choice or opt-in for the enforced language.

Content

No source excerpt is available for this finding.