cost-model

Implement per-provider cost models and budget policies for AI expenditure.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill cost-model-aesopscott
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cost-model
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/cost-model
Command: npx skills add https://github.com/AesopScott/mojo --skill cost-model-aesopscott

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the lack of granular financial control over AI model usage by providing a framework for implementing per-provider cost models and budget-policy enforcement.

Core Features & Use Cases

  • Budget Policy Authoring: Define specific rules for token accounting, halt thresholds, and request demotion.
  • Capability Control: Add new AI capabilities while ensuring they remain within strict, pre-defined cost boundaries.
  • Use Case: If you are integrating a new LLM provider, use this Skill to set a hard spending limit and a pre-check policy that blocks requests if the estimated token cost exceeds your project budget.

Quick Start

Use the cost-model skill to define a new budget policy that halts requests when the daily spend for the current provider exceeds fifty dollars.

Frequently Asked Questions about cost-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement pre-execution budget validation for LLM API requests?

Pre-execution budget validation filters AI requests by estimating token costs against per-provider cost models and custom budget policies before execution. This enforces strict financial guardrails by halting or demoting requests that exceed defined spending limits.

What is token accounting and how does it manage AI expenditure?

Token accounting tracks LLM usage costs to manage AI expenditure through customized budget policies. It applies halt thresholds to block requests when daily spend limits are exceeded, ensuring capability expansion remains within strict financial boundaries.

Can I set a hard spending limit for a specific LLM provider?

You can set hard spending limits for specific LLM providers using budget-policy authoring. This framework implements per-provider cost models with pre-check policies that automatically block requests if estimated token costs exceed your project budget.

How do I author budget policies that halt automated requests when daily spend exceeds a threshold?

Authoring budget policies involves defining rules for token accounting and halt thresholds to manage AI spend. You configure automated request filtering to block execution when the daily spend for a provider reaches your specified limit, like fifty dollars.

Does this approach work for FinOps governance in software engineering workflows?

This approach supports FinOps governance in software engineering workflows by applying strict financial guardrails to capability expansion. It satisfies requirements for token accounting, halt thresholds, and pre-execution budget validation to manage AI expenditure.

What are the limitations of using budget policies for request demotion?

Budget policies for request demotion limit AI expenditure by downgrading or blocking requests based on token cost estimates. The limitation is that pre-execution validation relies on estimated costs, requiring accurate per-provider cost models to enforce halt thresholds effectively.