product-price-monitor — Claude Code skill: what it does & setup
product-price-monitor tracks all-in prices for goods, flights, or hotels and triggers alerts upon hitting target thresholds. Filters repeated notifications.
MIT 160 installs ★ 265,216 updated 2026-10-25
npx skills add NousResearch/hermes-agent --skill product-price-monitor -a claude-codeWhat product-price-monitor does
The skill anchors exact item parameters: URL, seller, variant ID, dates, and cancellation terms. It inspects live pages via web_extract or browser_exec to separate base pricing from taxes, mandatory fees, and shipping costs. Currency conversions use timestamped exchange rates. The skill leaves one-off price lookups to direct web search tools.
Scheduling a recurring watch requires a working foreground fetch first. The baseline observation and parameters are saved to ~/.hermes/price-watches/<watch-slug>.json, followed by a cronjob schedule. Network failures mark the current state as unknown. The runner never overwrites valid historical observations with error pages and remains silent until prices change.
What it helps with
- track product discounts with shipping and taxes included
- watch flight tickets for cabin class price drops
- monitor hotel listings for refundable room availability
- prevent duplicate notifications on unchanged prices
Example prompts for the agent
- Alert me when this laptop drops below $1,000 including shipping.
- Track these flight dates and ping me if fares go under $500.
- Notify me as soon as this hotel has a refundable room open.
How to install product-price-monitor
1Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill product-price-monitor -a claude-code2Manually: put the files in place
~/.claude/skills/product-price-monitor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/product-price-monitor/
1Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill product-price-monitor -a codex2Manually: put the files in place
.agents/skills/product-price-monitor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill product-price-monitor -a cursor2Manually: put the files in place
.cursor/skills/product-price-monitor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NousResearch/hermes-agent skills/productivity/product-price-monitor2Manually: put the files in place
.github/skills/product-price-monitor/SKILL.md1Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill product-price-monitor -a gemini-cli2Platform CLI
gemini skills install https://github.com/NousResearch/hermes-agent --path skills/productivity/product-price-monitorManually: put the files in place
.devin/skills/product-price-monitor/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NousResearch/hermes-agent --skill product-price-monitor -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about product-price-monitor
How to install product-price-monitor in Claude Code?
Run npx skills add NousResearch/hermes-agent --skill product-price-monitor -a claude-code. The skill writes its instructions to ~/.claude/skills/product-price-monitor/SKILL.md.
What tasks does product-price-monitor avoid?
It is not built for immediate one-time price queries. Direct lookups should use web_search or web_extract instead.
Where does product-price-monitor keep its tracking state?
Parameters, baseline observations, and alert cooldown fingerprints are saved under ~/.hermes/price-watches/<watch-slug>.json. Scheduled runs check this file to prevent duplicate alerts.
Source text
SKILL.md · MIT
---
name: product-price-monitor
description: "Watch product, flight, or listing prices; alert on target."
version: 0.1.0
author: Ben Barclay (benbarclay), Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
hermes:
tags: [Prices, Availability, Shopping, Travel, Alerts]
related_skills: [maps]
---
# Product Price Monitor
Monitor a concrete purchasable item and alert on a normalized all-in price or availability condition. Handle variants, taxes, fees, currencies, stock, cancellation terms, and duplicate alerts explicitly. Setup runs once in the foreground; the recurring check runs as a `cronjob` tick (the `price-watch` automation blueprint scaffolds this).
## When to Use
- "Alert me when this laptop drops below $1,000."
- "Watch these flights for a fare under $500."
- "Tell me when this hotel has a refundable room."
- "Track ticket/listing availability."
- A cron tick fires for an existing price watch (steps 4-6).
Don't use for: one-off "what does this cost right now" lookups (use `web_search`/`web_extract` directly).
## Procedure — Setup (foreground, once)
### 1. Define the exact item
Record source URL/provider, product/listing ID where available, variant, quantity, location, dates, travelers/guests, membership/login assumptions, condition, seller, and acceptable substitutes. Done when two variants cannot be confused.
### 2. Define the alert condition
Specify currency, all-in vs pre-tax price, maximum price, availability/stock rule, shipping, refundability, cabin/room/ticket class, cooldown, and notification destination. Done when synthetic examples have deterministic alert decisions.
### 3. Establish a live baseline, then schedule
Fetch a bounded live result with `web_extract` or `browser_exec` and record retrieval time, source price, fees/taxes, availability, and terms. Do not schedule until one foreground fetch works. Write the watch contract (item, condition, baseline observation) to a state file under `~/.hermes/price-watches/<watch-slug>.json`, then create the job:
```
cronjob(action="create",
schedule="every 6h",
prompt="Load the product-price-monitor skill and run the tick for the watch contract at ~/.hermes/price-watches/<watch-slug>.json.",
deliver=<user's destination>)
```
Pick a cadence that respects rate limits and site terms. Done when the baseline matches the exact item contract and the job exists.
## Procedure — Tick (each scheduled run)
### 4. Fetch and normalize
Re-fetch the source. Convert currency only with a timestamped rate and retain the source currency. Separate base price, mandatory fees, shipping/taxes, total, and availability. Exclude volatile page metadata. A failed fetch means unknown state: report or skip, but never overwrite the last good observation with an error page. Done when the observation is comparable to the baseline or explicitly marked failed.
### 5. Compare and suppress duplicates
Alert on threshold entry, qualifying availability, material lower price, or recovery as requested. Store the last good observation and last alert fingerprint in the state file. Replaying the same offer must send no second alert; respect the cooldown. Done when the alert decision is deterministic against stored state.
### 6. Deliver or stay silent
When a condition is met, the alert includes: exact item/variant, observed all-in price and source currency, availability/terms, threshold, retrieval timestamp, source link, and important uncertainty. Never claim inventory is reserved. When nothing qualifies, stay silent — no "still watching" noise unless a periodic all-clear was requested. Done when the state file reflects this run.
## Pitfalls
- Comparing a base fare with an all-in threshold.
- Alerting on the wrong size, seller, cabin, dates, or room terms.
- Overwriting a last-known-good value with an error page.
- Polling aggressively enough to trigger blocking or violate site terms.
- Scheduling before a single foreground fetch has succeeded.
## Verification
- [ ] The watch contract pins the item so two variants cannot be confused.
- [ ] One foreground fetch succeeded before any job was created.
- [ ] Alert decisions replay deterministically from the state file; duplicates suppressed.
- [ ] Failed fetches never replaced last-known-good state.
- [ ] Alerts carry all-in price, source currency, timestamp, and source link.
© Ben Barclay (benbarclay), Hermes Agent · MIT · NousResearch/hermes-agent