retry-cap

Caps fallback tier to prevent expensive AI model escalation during retries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents silent, expensive escalations in AI model usage by capping the fallback tier during retry operations.

Core Features & Use Cases

  • Cost Efficiency Control: Enforces strict boundaries on which models are permitted during retry cycles.
  • Harness Inspection: Provides a structured runbook for reviewing and modifying fallback logic.
  • Use Case: When a primary model fails, use this Skill to ensure the system does not automatically switch to a significantly more expensive model, keeping token usage and costs within defined limits.

Quick Start

Use the retry-cap skill to inspect the current fallback configuration and apply a cap to prevent escalation to pricier models.

Frequently Asked Questions about retry-cap

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

FAQPage Schema
How do I prevent expensive model fallback during AI retry operations?

To prevent expensive model fallback during AI retry operations, apply a strict cap on fallback tier escalation. This enforces defined boundary rules to ensure retries do not automatically switch to pricier models, keeping token expenditure within budget.

What is fallback tier escalation in model management?

Fallback tier escalation in model management is the process of switching to alternative AI models when a primary model fails. Without a cap, this mechanism can silently escalate to significantly more expensive models, causing unexpected token cost spikes.

How do I enforce cost efficiency boundaries for prompt engineering workflows?

Enforce cost efficiency boundaries for prompt engineering workflows by inspecting your fallback configuration and applying a cap. This restricts model selection during retry cycles, verifying cost-saving outcomes through positive and boundary testing.

Can I inspect and modify existing retry fallback logic?

Yes, you can inspect and modify existing retry fallback logic using a structured runbook. This harness inspection process allows you to review current configurations and apply strict boundaries to prevent silent cost escalations.

Why does my token usage spike when the primary AI model fails?

Token usage spikes when a primary AI model fails because the system automatically escalates to a higher, more expensive fallback tier. Applying a cap restricts this escalation, ensuring retries stay within defined cost limits.

Do I need specific dependencies to cap fallback tiers?

No specific dependencies are required to cap fallback tiers. The system operates independently to inspect your model management configuration and enforce strict boundary rules for cost efficiency during retry operations.