Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - Handles platform-specific page structures (see [PLATFORMS.md](references/PLATFORMS.md))
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed e-commerce price monitor; its file writes, notifications, and optional scheduled scans fit that purpose.
Before installing, confirm that you want the agent to visit the listed product URLs, save price and alert data locally, and create any recurring scan only after you explicitly request and review its schedule.
Referenced artifact was not completely inspected
- Handles platform-specific page structures (see [PLATFORMS.md](references/PLATFORMS.md))
Referenced artifact was not completely inspected
- Handles platform-specific page structures (see [PLATFORMS.md](references/PLATFORMS.md))
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
cted via Discord, alerts route there automatically.
The agent should set up a recurring cron job when the user asks for automatic scanning:
Every 6 hours: scan tracked products, check alerts, notify if triggered
Every 24 hours: generate and save a daily summary report
Weekly (Monday): generate weekly comparison report
# Example — add to user's crontab or OpenClaw cron
openclaw cron add --name "price-scan" \
--schedule '{"kind":"every","everyMs":21600000}' \
--payload '{"kind":"agentTurn","message":"Run scheduled price scan on all tracked products. Check alerts and notify me of any changes."}'
scripts/price_history.jsonl
Each line is a JSON object:
{
"timestamp": "2026-04-30T10:00:00",
"product_id": 1,
"product_name": "iPhone 15 Pro",
"price": 4899.00,
"currency": "RM",
"url": "https://shopee.com.my/...",
"seller": "Apple Flagship Store",
"in
The skill description contains broad, high-level trigger language such as 'Use when the user wants to' followed by multiple loosely scoped intents. This can cause the agent to invoke the skill for general competitor research, reporting, or alerting requests even when the user did not specifically ask to use this skill, increasing the chance of unintended web access and file writes.
The natural-language setup examples instruct the agent to accept URLs and begin monitoring based on conversational input, but they do not clearly constrain when activation should occur or require explicit confirmation of side effects. In practice, this ambiguity can lead to accidental enrollment of targets, scheduled scans, or persistent storage from casual user messages or quoted text.
The file instructs the agent to create a recurring cron job that persists beyond the current session, but it does not explicitly require clear user consent or warn that this creates an ongoing automated task in the user's workspace/system. In an agent skill context, persistence is security-relevant because it can continue consuming resources, performing network activity, and generating notifications after the original interaction is over.