Price Monitor
PassAudited by ClawScan on May 1, 2026.
Overview
The skill’s artifacts coherently implement browser-based price monitoring, with only user-directed web visits, local logging, and optional scheduling to review before use.
Before installing or using it, review the product CSV, ensure agent-browser is trusted, run it manually before adding any schedule, and only monitor sites in ways that comply with their rules and your intended use.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or untrusted CSV could cause the agent-browser to visit unintended sites and record extracted page text in the local history file.
The script drives browser automation to open every URL supplied in the CSV and then extract text with a selector. This is central to the skill’s purpose, but users should verify the product list before running it.
stdout, stderr, code = run_agent_browser(["open", url])
Use product CSV files you trust, review URLs and selectors before running, and keep rate limits appropriate for the target sites.
The skill’s behavior depends on the agent-browser binary available in the user’s environment.
The included script depends on an external agent-browser command, while the registry metadata does not declare required binaries or an install spec. This is a setup/provenance note rather than hidden behavior.
cmd = ["agent-browser"] + args
Confirm that agent-browser is installed from a trusted source and is the expected version before running the monitoring script.
If the user adds the cron job, the skill will keep visiting configured sites and appending history until the schedule is removed.
The documentation provides a cron example for scheduled daily checks. It is user-directed and not automatically installed, but it can make the monitoring continue over time if the user enables it.
0 9 * * * cd /path/to/skill && python scripts/monitor_prices.py products.csv
Only add the cron schedule intentionally, document where it is installed, and remove it when monitoring is no longer needed.