openrouter-cost-controls

Implement budget controls and cost limits for OpenRouter. Use when managing spending or preventing overruns. Trigger with phrases like 'openrouter budget', 'openrouter spending limit', 'cost control', 'openrouter billing alert'.

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill provides comprehensive budget management and cost control features for OpenRouter API usage. It enables users to implement per-key spending limits, set up automated billing alerts, and establish hard cutoffs to prevent unexpected financial overruns, ensuring predictable and managed AI operational expenditures.

Use Cases

  • 1. Budget Overrun Prevention: Automatically set hard spending caps to stop API usage once a predefined budget is reached, protecting against unexpected billing spikes.
  • 2. Granular Cost Allocation: Implement per-key limits to track and control AI expenses across different departments, clients, or specific development projects.
  • 3. Proactive Financial Monitoring: Configure automated alerts that trigger when spending hits specific thresholds, allowing for real-time oversight of API costs.
  • 4. Operational Guardrails: Deploy automatic cutoffs to mitigate financial risks associated with runaway processes, infinite loops, or unauthorized API usage.
nameopenrouter-cost-controls
description|
allowed-toolsRead, Write, Edit, Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Openrouter Cost Controls

Overview

This skill demonstrates implementing cost controls including per-key limits, budget alerts, and automatic cutoffs.

Prerequisites

  • OpenRouter account
  • Budget requirements defined

Instructions

Follow these steps to implement this skill:

  1. Verify Prerequisites: Ensure all prerequisites listed above are met
  2. Review the Implementation: Study the code examples and patterns below
  3. Adapt to Your Environment: Modify configuration values for your setup
  4. Test the Integration: Run the verification steps to confirm functionality
  5. Monitor in Production: Set up appropriate logging and monitoring

Output

Successful execution produces:

  • Working OpenRouter integration
  • Verified API connectivity
  • Example responses demonstrating functionality

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources