Back to skill

Security audit

Apollo Circadian

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed local scheduling helper that reads a heartbeat time file and writes a small local phase-state file, with no evidence of network access, credential use, or destructive behavior.

Install only if you want periodic circadian scheduling advice. Review the broad activation triggers, heartbeat integration, hardcoded Asia/Shanghai personal schedule, and /root state path before enabling it in a shared or non-root environment.

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 (2)

Vague Triggers

Medium
Confidence
82% confidence
Finding
The activation conditions are broad and ambiguous, including generic mentions of time, prioritization, and 'every heartbeat trigger.' In an agent system, overly broad triggers can cause unintended auto-invocation, making the skill influence many conversations or workflows where it was not explicitly requested, which can disrupt task routing and create an unsafe control surface for downstream behaviors.

Vague Triggers

Medium
Confidence
88% confidence
Finding
Using '每次心跳触发时' as an activation condition without defining the heartbeat source, trust boundary, or applicable contexts enables the skill to run automatically on recurring system events. In this skill, that automatic path reads a file under /tmp and can influence recommendations or workflow transitions, so unclear heartbeat semantics increase the risk of unintended execution and unsafe dependence on ambient state.

Static analysis

No suspicious patterns detected.