claude/ai-resources-plugin/skills/model-price-compare/SKILL.md
Compare AI model prices across Anthropic, OpenAI, and Google. Generates pages-per-dollar / cost-per-token visualizations.
npx skillsauth add amhuppert/my-ai-resources model-price-compareInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate an interactive HTML visualization comparing pricing and capabilities of frontier AI models across major providers. Always research live pricing data — never rely on training knowledge.
Research the current pricing for these frontier model families:
| Provider | Models | |----------|--------| | Anthropic | Claude Opus 4.6, Claude Sonnet 4.6, Claude Haiku 4.5 | | OpenAI | GPT-5.4 family (GPT-5.4, GPT-5.4-mini, GPT-5.4-nano) | | Google | Latest Gemini models (Gemini 2.5 Pro, Gemini 2.5 Flash, etc.) |
The models listed above are baseline targets. If newer versions exist (e.g., a model listed as 4.6 is now 5.0), use the current versions. Include additional frontier models discovered during research that belong to these product lines. Exclude deprecated, preview, or fine-tuning-only variants.
Search for the official API pricing page of each provider. For each model, collect:
| Field | Description |
|-------|-------------|
| provider | Anthropic, OpenAI, or Google |
| model | Display name (e.g., "Claude Sonnet 4.6") |
| inputPrice | USD per 1M input tokens |
| outputPrice | USD per 1M output tokens |
| contextWindow | Maximum context window in tokens |
Use standard real-time API pricing. If a provider offers tiered pricing (batch, cached, etc.), use the default non-batch, non-cached tier.
Pages per dollar — approximate one page as 800 tokens:
pagesPerDollarInput = 1,000,000 / inputPrice / 800
pagesPerDollarOutput = 1,000,000 / outputPrice / 800
Create a self-contained HTML file saved as model-price-comparison.html in the current working directory.
Refer to references/visualization-spec.md for the complete HTML structure, Chart.js configurations, and styling guidelines.
Use consistent colors across all charts:
| Provider | Color | Hex |
|----------|-------|-----|
| Anthropic | Coral | #D97757 |
| OpenAI | Green | #10A37F |
| Google | Blue | #4285F4 |
After generating the HTML file:
references/visualization-spec.md — HTML page structure, Chart.js chart configurations, table styling, and responsive layout patternstools
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
development
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
tools
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.
documentation
This skill should be used when integrating source material into a knowledge base, including when the user asks to "integrate this document into the knowledge base", "add this transcript to the memory bank", "ingest this document", "update the knowledge base", "analyze a new source document", or "sync current-state docs with this source".