Skip to content
cccskills
FreePublished on GitHub

credit-optimizer

Automatically optimize AI agent credit usage by routing tasks to the most cost-efficient execution path. Use when you want to reduce AI API costs by 30-75% without quality loss, classify task complexity before execution, route simple tasks to free or low-cost models, split complex tasks into optimized sub-tasks, or detect vague prompts before wasting credits.

The English summary is being prepared. Showing the original description.

See how to install

Files included (14)

  • SKILL.md4.0 KB
  • .github/workflows/health-check.yml5.3 KB
  • .github/workflows/publish.yml3.6 KB
  • .gitignore124 B
  • AGENTS.md2.5 KB
  • CHANGELOG.md2.1 KB
  • LICENSE1.0 KB
  • manifest.json783 B
  • mcp_credit_optimizer/__init__.py137 B
  • mcp_credit_optimizer/__main__.py120 B
  • mcp_credit_optimizer/server.py25.7 KB
  • pyproject.toml1.5 KB
  • README.md9.2 KB
  • server.json864 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Credit Optimizer v5

Automatically optimize AI agent credit/token usage by routing tasks to the most cost-efficient execution path — with zero quality loss.

Audited across 53 real-world scenarios. 30-75% cost savings. 0% quality degradation.

When to Use This Skill

  • Before executing any AI task that consumes credits or tokens
  • When you want to minimize API costs without sacrificing output quality
  • When processing batches of tasks with varying complexity
  • When you need to decide between different model tiers (free/standard/premium)

How It Works

Step 1: Task Classification

Analyze the incoming task and classify it into one of these categories:

CategoryExamplesTypical Savings
Simple Q&ADefinitions, facts, conversions90-100% (use free tier)
Code GenerationScripts, functions, refactoring40-60%
ResearchMulti-source analysis, synthesis20-40%
Creative WritingArticles, stories, marketing copy30-50%
Data AnalysisCSV processing, visualization40-70%
Complex ReasoningMulti-step logic, architecture10-20%

Step 2: Prompt Quality Check

Before executing, evaluate the prompt:

  1. Clarity Score (1-10): Is the request specific enough?

    • Score < 5: Ask for clarification BEFORE executing (saves wasted credits)
    • Score 5-7: Add reasonable assumptions and proceed
    • Score 8+: Execute directly
  2. Scope Detection: Can this be split into smaller, cheaper sub-tasks?

    • If YES: Break into atomic tasks, route each independently
    • If NO: Route as single task
  3. Data Requirement Check: Does this need real-time data?

    • If YES: Use tools/search first, then process with cheaper model
    • If NO: Use internal knowledge with appropriate model tier

Step 3: Model Routing

Route to the optimal execution path:

IF task is simple Q&A or formatting:
  → Use FREE tier / Chat mode (no credits)
  
IF task is medium complexity (code, writing, basic analysis):
  → Use STANDARD tier
  
IF task requires deep reasoning, multi-step logic, or creative excellence:
  → Use PREMIUM/MAX tier
  
IF task is mixed complexity:
  → SPLIT into sub-tasks and route each independently

Step 4: Execution Optimization

During execution, apply these optimizations:

  • Context Pruning: Only include relevant context, not entire conversation history
  • Output Scoping: Request specific output format to avoid verbose responses
  • Caching: Check if similar tasks were recently completed
  • Batch Processing: Group similar sub-tasks for efficient processing

Efficiency Directives

  1. Never use premium models for tasks that standard can handle equally well
  2. Always check if the task can be answered from cached/known information first
  3. Split compound requests into atomic tasks before routing
  4. Ask for clarification on vague prompts — it's cheaper than re-doing work
  5. Use structured output formats to reduce token waste

Audit Results Summary

MetricResult
Scenarios tested53
Average savings30-75%
Quality loss0%
Quality improvement cases2
False routing rate< 3%

Links

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.

Report a problem with this skill