budget-negotiator

Drafts ROI-based token budget increase requests when autonomous loops near their daily cap.

10.8k|1.5k|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/cobusgreyling/loop-engineering --skill budget-negotiator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: budget-negotiator
Source: https://github.com/cobusgreyling/loop-engineering/tree/main/skills/budget-negotiator
Command: npx skills add https://github.com/cobusgreyling/loop-engineering --skill budget-negotiator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous agent loops that hit their daily token budget normally exit silently, leaving critical work like failing CI or security vulnerabilities unfinished. This Skill lets the agent justify and formally request a budget extension instead of abandoning high-priority tasks.

Core Features & Use Cases

  • ROI Calculation: Reads loop-run-log.md to sum actions taken, successful outcomes, and token spend for the day before making any request.
  • Structured Escalation: Appends a clearly formatted [BUDGET NEGOTIATION] request to the High Priority section of STATE.md so a human maintainer can make a quick yes/no decision.
  • Strict Safety Limits: Caps requests at +20% or +50k tokens, allows only one negotiation per day, forbids self-editing of loop-budget.md, and reverts to report-only mode if declined.
  • Use Case: A daily triage loop burns 95k of its 100k token cap but has one critical CI failure remaining; the agent drafts a justification citing its four successful fixes and requests a +50k extension, then suspends until a human approves.

Quick Start

When the loop-budget skill reports 90% or more of the daily token cap is spent and high-priority items remain, activate this skill to draft a budget negotiation request in STATE.md.

Frequently Asked Questions about budget-negotiator

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

FAQPage Schema
How do I stop an autonomous agent loop from failing silently at its token cap?

Use a budget negotiation protocol that activates when spend reaches 90% of the daily cap. The agent calculates its ROI from the run log, drafts a justification, and escalates a tagged request to STATE.md instead of exiting silently.

How does the agent justify a token budget increase?

The agent reads loop-run-log.md to sum actions_taken, successful outcomes, and tokens_estimate for the day, then checks STATE.md for remaining high-priority items. It drafts a request citing current spend, completed work, and the specific cap field to increase.

Can the agent raise its own token budget limit?

No. The agent is strictly forbidden from editing loop-budget.md itself. A human must explicitly increase the cap, and the agent only resumes after verifying the change on a subsequent run.

What are the limits on budget negotiation requests?

Requests are capped at +20% or +50k tokens per negotiation, with a maximum of one negotiation per day. If a human declines by removing the tag without increasing the budget, the agent reverts to report-only mode and does not ask again that day.

When should budget negotiation not be used?

It should not activate when remaining work is not high priority; in that case the standard loop-budget exit sequence applies. It is also inappropriate outside L3 unattended loops where a human is already supervising spend.