Cost Protection with Multi-Layer Timeout Limits

James Phoenix
James Phoenix

Summary

Runaway LLM workflows can rack up hundreds of dollars in unexpected API costs. Implement multi-layer timeout protection at job level (GitHub Actions timeout-minutes), request level (max_tokens), and input level (sample size limits) to cap costs at predictable levels. For scheduled scans: $0.12/scan × 120 scans/month = $14.40/month maximum.

The Problem

Autonomous LLM workflows in CI/CD can enter infinite loops, process excessive files, or generate bloated responses, leading to surprise bills of $100+ from runaway API usage. Without hard limits, a single misconfigured job can consume an entire monthly budget in hours.

The Solution

Set strict timeout limits at multiple layers: GitHub Actions job-level timeouts (15 min), LLM request-level token caps (max_tokens: 4096), input sample size limits (50 files max), and model selection (fast, cheap Sonnet). This creates fail-safe protection where even if one layer fails, others prevent cost explosions.

Leanpub Book

Read The Meta-Engineer

A practical book on building autonomous AI systems with Claude Code, context engineering, verification loops, and production harnesses.

Continuously updated
Claude Code + agentic systems
View Book

Related Concepts

References

Topics
Agent ReliabilityApi DesignAutomationCi CdCost OptimizationReliabilityWorkflows

Newsletter

Become a better AI engineer

Weekly deep dives on production AI systems, context engineering, and the patterns that compound. No fluff, no tutorials. Just what works.

Join 306K+ developers. No spam. Unsubscribe anytime.


More Insights

Cover Image for Hand Off Between Agent Subscriptions Before You Run Out of Weekly Usage

Hand Off Between Agent Subscriptions Before You Run Out of Weekly Usage

The session about to hit its weekly limit is the single best-informed writer of the brief that lets a different vendor’s agent pick up the work. Spend the last of the allowance on that brief, not on one more edit.

James Phoenix
James Phoenix
Cover Image for Use an Expensive Model to Build a Cheap Agentic Runtime

Use an Expensive Model to Build a Cheap Agentic Runtime

The model that writes the harness and the model that runs inside it do not have to be the same model. They probably should not be.

James Phoenix
James Phoenix