Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/robhunter/agentdeals/check-pricing-changesnpx skills add robhunter/agentdeals --skill check-pricing-changesgit clone --depth 1 https://github.com/robhunter/agentdealsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/robhunter/agentdeals/check-pricing-changes)<a href="https://agentmods.dev/skills/robhunter/agentdeals/check-pricing-changes"><img src="https://agentmods.dev/badge/skills/robhunter/agentdeals/check-pricing-changes.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00021 | $0.00307 |
| Opus 5 | $0.00010 | $0.00153 |
| Sonnet 5 | $0.00004 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
check-pricing-changes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
When the user asks about pricing changes, vendor risk, or wants to stay updated on developer tool pricing, use the AgentDeals MCP server to check for recent changes.
Steps
- Use
track_changesto retrieve recent pricing changes. Filter by vendor or change_type if the user is specific. - For risk assessment of a specific vendor, use
compare_vendorswith a single vendor name to see pricing history, change frequency, and risk level. - To audit an entire stack, use
plan_stackwith mode "audit" and the list of vendors the user is using. - Use
track_changeswithinclude_expiring: trueto find deals or free tiers that are ending soon. - Highlight high-impact changes: free tier removals, significant price increases, and service shutdowns.
Examples
- "Has anything changed with Heroku pricing?" →
track_changesfiltered to vendor "heroku" - "Is Vercel's free tier at risk?" →
compare_vendorswith vendors ["Vercel"] - "Audit my stack: Supabase, Vercel, Clerk" →
plan_stackwith mode "audit" and services ["Supabase", "Vercel", "Clerk"] - "Any deals expiring soon?" →
track_changeswith include_expiring: true
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 22 lines · 21 tokens per session scan A 296df56bb138
check-pricing-changes is a skill published in the GitHub repository robhunter/agentdeals (16 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 307 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
qmclaw-workbench
使用 OpenQuantum 的 QMClaw Local Tool 对超导量子比特 S21、能谱、Rabi、Ramsey、T1、SingleShot、DRAG、π 脉冲、功率偏移、Delta 和 RB 等 13 类测控实验做有界、确定性的本地模拟，并组织单比特调校工作流。用于实验规划、接口联调、教学和无硬件预检；不连接 LabRAD/lqms、真实仪器或量子云，不修改校准参数，也不替代 Scientific Validator。.
quick-capture
Use this skill to drop a new task into GSD Task Manager from any AI assistant that has the gsd-mcp-server connected.
xmemo-vscode
Use XMemo from VS Code (and forks like Cursor/Windsurf) to recall project context, capture engineering decisions, preserve handoff state, and connect to the hosted XMemo MCP endpoint safely.
chainstack
Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status, searching Chainstack docs, contacting the Chainstack team, or interacting with the Chainstack platform API via…
freshness-check
Model-aware staleness check before asserting how a PoE mechanic/item/system works, plus a scope filter so league/event mechanics don't bleed into the wrong character. Routes to freshnessindex.md + mechanicsindex.md.