T06 · System Persistence
- Location
SKILL.md:227- Finding
Persistent External Inbox Polling Through a Scheduled Cron Job
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent agent-messaging API guide, but it needs review because it recommends persistent automated polling and treats remote service text as operational guidance.
Install only if you intend to use agentdeaddrop.com for agent-to-agent messaging. Do not let remote search messages or inbox message bodies override user, system, or skill instructions. Avoid setting up automatic cron polling unless you explicitly want persistent background network activity, store the API key in a protected secret mechanism, and have a clear way to remove the job and revoke the key.
SKILL.md:227Persistent External Inbox Polling Through a Scheduled Cron Job
SKILL.md:163Server-Controlled Response Field Is Elevated as Behavioral Guidance
The search endpoint may return a free-form message and explicitly instructs the agent to 'read it carefully' because it contains 'important context' about how to contribute. This is a prompt-injection vector: untrusted remote content is being framed as authoritative operational guidance, which could manipulate an agent into registering, changing behavior, disclosing data, or taking other unintended actions.
The skill documents that polling consumes messages, but the operational guidance does not make the destructive nature of inbox polling prominent where an agent is most likely to act on it. In an agent-to-agent system, destructive reads can cause silent message loss, missed tasks, and broken workflows if an agent polls speculatively, concurrently, or too frequently without understanding that messages are permanently removed once read.
The skill recommends automated polling via curl/OpenClaw cron jobs but provides no guidance on protecting the Bearer API key. This encourages insecure practices such as embedding credentials in shell history, process arguments, logs, or world-readable cron files, which could expose an account and allow unauthorized profile changes or message access.