菜单
Refresh a model vendor's price table in data/prices/ with cited sources. This is the daily price-freshness loop body — use when the user asks to update prices, check for price changes, or refresh a vendor's rates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
File an issue on this repo's GitHub tracker (anandgupta42/receipts) via `gh issue create`. Use when the user asks to file, add, or track an issue for aireceipts. This repo's issues live on GitHub — do not file them into any local or external issue tracker.
Cut an aireceipts release: verify the version tag matches the manifest, generate a changelog from conventional commits, and prep for npm publish (human clicks). Use when the user asks to release, cut a version, or publish a new version.
Adversarially validate a draft spec BEFORE the maintainer sees it. Use after write-spec finishes, or when the user asks to validate/review a spec. A draft without a validation record cannot be approved or built.
Implement an approved spec end-to-end for aireceipts, including agent-team waves for milestone (M-file) specs. Use when the user says implement/build/ship a spec (e.g. 'build SPEC-0001', 'ship M1').
Critically review an aireceipts PR as an independent critic — different model family from whoever built it, audits test-diffs hardest. Use when asked to review a PR, act as the critic, or before landing/merging any change.
Multi-persona release vetting board — PM, EM, Designer, QA personas deeply analyze the release candidate; produces the signed verdict file WITHOUT which /release refuses to proceed. Use before any release, when asked to vet a release, or when cutting a version.
| name | update-prices |
| description | Refresh a model vendor's price table in data/prices/ with cited sources. This is the daily price-freshness loop body — use when the user asks to update prices, check for price changes, or refresh a vendor's rates. |
| trigger | /update-prices |
Every price-row change needs a sources: entry with a URL you actually fetched and
read. Never invent or infer a price. The block-price-edit-without-citation hook
enforces this mechanically (exit 2 on a data/prices/** edit with no sources in the
diff) — this skill exists to make sure you clear that bar honestly, not to work around
it.
Pick a single vendor's price page (the vendor's own pricing page or API pricing docs —
not a third-party aggregator, which can be stale). Fetch it. Read data/prices/README.md
for the exact schema (price_history rows: input, output, input_cached, from_date, to_date, sources[]).
price_history row by setting its to_date
to the day before the new rate took effect, then append a new row with the new
rate and from_date — never edit a historical row's numbers. Old sessions must still
price at the rate that was live when they ran (I3).Each sources entry is the exact URL of the page that states the price, not the
vendor's homepage. If the page requires interpretation (e.g. a tiered rate), quote the
relevant line in the PR description so a human reviewer doesn't have to re-derive it.
Run node scripts/cite-check.ts (verifies cited URLs resolve and the claimed price
appears on the page) and the unmasked verification block. Both must pass.
Title: chore(prices): update <vendor> rates. Body: what changed, the cited URL(s), and
the effective date. One vendor per PR keeps review fast and the diff auditable.