Security audit

Cron Cost Guard

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent cron-auditing runbook, but users should confirm the exact job before removing any cron entry.

Before using the repair steps, verify the exact cron job ID, capture relevant job configuration and log context, then remove only the confirmed offending job. The skill is otherwise a narrow Markdown runbook for diagnosing and preventing costly cron retry loops.

A.I.G

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

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (1)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The document instructs the operator to immediately remove a cron job as part of incident response, but it provides no warning to verify the target job ID, capture evidence, or consider safer containment steps first. In an operational runbook used by agents or humans under pressure, this increases the risk of accidental deletion of the wrong job and loss of forensic context, which can disrupt service and hinder recovery.
Content: No source excerpt is available for this finding.