Skip to content
cccskills
FreePublished on GitHub

model-cost-compare

Compare estimated AI model costs for a task using its complexity and expected text volume. Get a suitable low-cost recommendation, a cheaper but riskier alternative, and a premium option, with explicit assumptions behind the estimates.

OriginalShow the original description

Starter: compare model costs for a described task — maps task shape to the cheapest adequate seat and shows the price spread

See how to install

Good for

  • Choosing a model for a bulk code refactor
  • Comparing model costs for a security review
  • Estimating costs for long-document analysis
  • Finding a budget option for simple edits

Files included (2)

  • SKILL.md2.8 KB
  • agents/openai.yaml169 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Model Cost Comparison (Starter Pack)

Answer "which model should I use for this, and what will it cost?" with numbers instead of vibes.

When to use

The user describes a task (bulk refactor, deep review, quick lookup, long-context analysis) and wants the cheapest seat that is still adequate.

Steps

  1. Classify the task. Bucket it: mechanical (rename, format), standard coding, hard reasoning (architecture, security review), long-context (>200K tokens input), or web research.
  2. Estimate volume. Rough input/output token estimate from the described scope (files touched × average size; state the assumption).
  3. Price the roster. Using the cost table in CLAUDE.md ($/MTok input/output), compute the estimated cost for each plausible seat: Claude Opus 5.5 (4/20 USD), Claude Opus 5 (5/25 USD), Claude Sonnet 5 (2/10 USD), Fable 5.1 (10/50 USD, 1M context, explicit-only), Codex GPT-5.6 Sol (4/20 USD), Terra (2/12 USD), Luna (0.20/1.20 USD), GPT-6 Astra (10/50 USD, explicit-only), Perplexity Sonar Pro (3/15 USD), and the included-cost seats (agy, copilot, ollama, cursor-agent) at 0 USD. For Astra requests above 272K input tokens, apply 2x input and 1.5x output pricing to the full request.
  4. Recommend one seat. Pick the cheapest adequate option and defend it in two sentences. Mechanical work goes to included or budget seats; hard reasoning justifies the current Opus default at high effort; only a bounded judgment-class call (ambiguous architecture, API design, product tradeoffs) justifies Fable 5.1 at 10/50 USD per MTok.
  5. Check risk surfaces. Regardless of the classification, escalate specifically to the current Opus default—Opus 5.5 on Claude Code v2.1.280+, otherwise Opus 5—when the task touches API or schema contracts, security-sensitive code or CI configuration, release artifacts, user-facing UI, a new module, or a breaking change. Fable 5.1 remains limited to bounded judgment-class calls and is never the security-audit seat. Astra is also explicit-only and does not provide independence from GPT-5.6. Cheap-seat agreement never settles a judgment-class decision.
  6. Show the spread. A three-row table: recommended seat, one cheaper-but-riskier option, one premium option, each with estimated dollars for this task.

Guardrails

  • Never recommend Fable 5.1, Astra, or fast-mode Opus by default; these premium seats are opt-in only.
  • Never recommend Fable 5.1 for security audits; its safety classifiers can refuse offensive-security phrasing. Security review goes to Opus 5 (see skills/blocks/fable5-prompting.md).
  • If the estimate exceeds 1 USD, say so explicitly before any dispatch happens.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

council-verdicts

FreeSummary

Interpret the saved results of a completed AI council review. Count verdicts, check whether enough participants responded and whether models are independent, surface substantive dissent, and explain what action the outcome supports.

  • Explain a completed council review
  • Check vote counts and quorum
  • Assess model independence and dissent
nyldn/claude-octopus4.3KUpdated Oct 21, 2026

debate-kickoff

FreeSummary

Turn a technical choice into a structured debate between different AI model families. Assign explicit positions, launch the discussion, and summarize agreement, disagreement, and a recommendation supported by the strongest argument that survives the debate.

  • Compare Redis and Memcached for session storage
  • Debate monorepo versus polyrepo organization
  • Examine a technical choice from opposing positions
nyldn/claude-octopus4.3KUpdated Oct 21, 2026

flow-define

FreeSummary

Clarify a feature’s requirements with multiple AI providers, combining technical constraints with user and business needs. Produce a scoped definition covering priorities, edge cases, exclusions, and a requirements checklist before implementation begins.

  • Defining requirements for a user authentication system
  • Setting boundaries for a notification feature
  • Identifying technical constraints and edge cases
nyldn/claude-octopus4.3KUpdated Oct 21, 2026

flow-deliver

FreeSummary

Review code or documents with available AI providers before delivery. Combine findings into a scored validation report that checks prior requirements and decisions, separates critical issues from warnings, and recommends next steps.

  • Review authentication code before release
  • Check API readiness before deployment
  • Review a PRD for missing requirements
nyldn/claude-octopus4.3KUpdated Oct 21, 2026

flow-develop

FreeSummary

Develop complex features or business documents by gathering approaches from available AI providers. Combine their perspectives with prior project decisions and quality checks to produce a proposed plan, then proceed with implementation after user confirmation.

  • Planning and implementing a complex feature
  • Comparing approaches for an external service integration
  • Developing a product requirements document or strategy
nyldn/claude-octopus4.3KUpdated Oct 21, 2026

flow-discover

FreeSummary

Research technical or business questions through multiple available AI providers, each assigned a different perspective. Combine usable results into a report covering findings, disagreements, evidence gaps, priorities, and recommended next steps.

  • Compare libraries and technical approaches
  • Research markets and competitor strategies
  • Synthesize literature from multiple perspectives
nyldn/claude-octopus4.3KUpdated Oct 21, 2026

See all skills by nyldn

Report a problem with this skill