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/firecrawl/web-agent/pricing-trackernpx skills add firecrawl/web-agent --skill pricing-trackergit clone --depth 1 https://github.com/firecrawl/web-agentWhat 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.00103 | $0.01179 |
| Opus 5 | $0.00051 | $0.00589 |
| Sonnet 5 | $0.00021 | $0.00236 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
pricing-tracker 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Tracker
Extract pricing tiers from a vendor's pricing page and normalize them into a consistent shape. Optimized for SaaS, API, cloud, LLM, and CDN pricing pages — all of which share similar structure but inconsistent naming.
When to use
- User provides a pricing URL: "get pricing from https://openai.com/api/pricing"
- User names a vendor: "what does Vercel cost?", "get Anthropic API pricing"
- User wants to compare prices across vendors (delegate per-vendor extraction to this skill, then aggregate)
- User wants to monitor pricing on a schedule (combine with
exportSkill: trueto generate a standalone workflow)
Do NOT use for e-commerce SKU pricing — use e-commerce instead.
Strategy
-
Find the pricing URL.
- If the user provided one, use it.
- Otherwise search
"<vendor> pricing"and take the top result from the vendor's own domain.
-
Scrape with
only-main-content. Pricing pages are heavy on nav and testimonials that waste context. -
Identify the unit. Every pricing page has one of these shapes — pick the right one:
- Per seat — SaaS (Notion, Linear, Vercel)
- Per request / token / call — API and LLM (OpenAI, Anthropic)
- Per GB / TB — storage, bandwidth, CDN
- Per minute / hour — compute (Modal, Replicate)
- Flat monthly — simple SaaS tiers
- Usage-based with tiers — cloud (AWS, GCP)
-
Extract every tier. Include Free and Enterprise even when their price is
$0or"Contact sales"— users care about those as much as the paid tiers. -
Flag the gotchas.
- Annual vs monthly pricing (often a 20% discount buried on annual)
- Overage rates past the included quota
- Seat minimums ("Team plan starts at 5 seats")
- Features gated to higher tiers
- "Free tier" that requires a credit card
-
Call
formatOutputonce with the full pricing object.
Quick start
// Single vendor
await agent.run({
prompt: 'Get OpenAI API pricing for every model',
urls: ['https://openai.com/api/pricing'],
skills: ['pricing-tracker'],
format: 'json',
})
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.
- 2d ago First seen · 113 lines · 103 tokens per session scan A bc0a65750829
pricing-tracker is a skill published in the GitHub repository firecrawl/web-agent (1,223 stars, last pushed 4mo ago), licensed MIT. It adds 103 tokens to every session and 1,179 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.