Agent skill

Budget Negotiator

by cobusgreyling in cobusgreyling/loop-engineering

An advanced skill for L3 autonomous loops. An agent skill from cobusgreyling/loop-engineering.

MITAuto-check passedAgent Workflows

Install Budget Negotiator

skills CLI
$ npx skills add cobusgreyling/loop-engineering --skill budget-negotiator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cobusgreyling/loop-engineering budget-negotiator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/budget-negotiator .claude/skills/budget-negotiator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
budget-negotiator
GitHub stars
11k
Used in
1 other repo
Token cost
~864 tokens
SKILL.md length
433 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

An advanced skill for L3 autonomous loops. An agent skill from cobusgreyling/loop-engineering.

  • Works in 4 steps: Calculate ROI → Draft Justification → Escalate to Humans → …
  • Tasks that involve Autonomous loops
  • SKILL.md covers Goal, Rules & Precedence and Negotiation Protocol
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Budget Negotiator is an agent skill from cobusgreyling/loop-engineering. An advanced skill for L3 autonomous loops. When the token budget nears exhaustion, the agent analyzes its ROI and autonomously drafts a negotiation request for a budget increase rather than silently failing.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Autonomous loops and LLM cost and token optimization. The repository describes itself as: Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny)… The licence is MIT.

When your agent uses it

  • Tasks that involve Autonomous loops
  • Tasks that involve LLM cost and token optimization

Example prompts

  • “/budget-negotiator”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Calculate ROI
  2. Draft Justification
  3. Escalate to Humans
  4. Resume

What it can do on your machine

Read from SKILL.md and the folder at commit f914d15. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Budget Negotiator loads about 864 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 433 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~864

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cobusgreyling/loop-engineering at commit f914d15, republished under its MIT licence (© cobusgreyling). 433 words, ~864 tokens.

Download SKILL.mdSave it as .claude/skills/budget-negotiator/SKILL.md (or your agent's skills folder).
name
budget-negotiator
description
An advanced skill for L3 autonomous loops. When the token budget nears exhaustion, the agent analyzes its ROI and autonomously drafts a negotiation request for a budget increase rather than silently failing.
<!--
  NOTE: This template is a mirror of skills/budget-negotiator/SKILL.md.
  Any changes made here must be kept byte-identical to the source skill.
-->

Budget Negotiator

When you detect that you are nearing your daily token cap (e.g., ≥90% spend) via the loop-budget skill, DO NOT just exit silently. You must negotiate for an extension based on your Return on Investment (ROI).

Goal

Ensure that critical work is not arbitrarily blocked by token budgets if the loop has demonstrated a high success rate and the remaining work is critical.

Rules & Precedence

  • Precedence: budget-negotiator ONLY activates when loop-budget would otherwise hard-exit (i.e. ≥90% spend), and ONLY when there are High Priority items remaining. If work is not High Priority, yield to the standard loop-budget exit sequence.
  • Safety: This skill touches L3 (unattended) safety boundaries. See Safety Boundaries for threat models.
  • Strict Cap Limitation: You are strictly forbidden from self-raising the caps in loop-budget.md. A human MUST explicitly edit loop-budget.md to increase the cap before you can resume.
  • Human Decline: If a human declines the negotiation by removing the [BUDGET NEGOTIATION] tag without increasing the budget, you must revert to report-only mode and NOT ask again today.
  • Cap the Ask: You may only request a maximum of +20% or +50k tokens per negotiation. You may only negotiate a maximum of one time per day.
Show full SKILL.md (235 more words)Show less

Negotiation Protocol

  1. Calculate ROI:

    • Read loop-run-log.md and sum up the actions_taken, outcome (specifically successes), and tokens_estimate fields for today.
    • Read STATE.md to identify the severity of the remaining actionable items in the Watch List or High Priority sections.
  2. Draft Justification:

    • If the remaining items are High Priority (e.g., CI is red, P0 bugs, security vulnerabilities), draft a concise business justification.
    • The justification must include:
      • The current spend vs the limit.
      • The exact actions_taken count and successful outcomes you've completed today based on the JSON log.
      • The specific critical issue(s) remaining.
      • A precise request for an extension tied to the specific loop-budget.md field (e.g., "Requesting +50k tokens for the 'Validate/Audit (CI)' max tokens/day").
  3. Escalate to Humans:

    • Append your request to the High Priority section of STATE.md with the tag [BUDGET NEGOTIATION].
    • Ensure the request is formatted clearly so a human maintainer can make a quick yes/no decision.
    • Example: [BUDGET NEGOTIATION] I have burned 95k/100k tokens for the 'Daily Triage' loop today. However, I have successfully executed 4 actions with a 'fix-proposed' outcome. There is 1 critical CI failure remaining on the main branch. I request a temporary bump of 'Daily Triage' max tokens/day by +50k to resolve it.
    • Set your internal state to WAITING_FOR_BUDGET and safely suspend execution.
  4. Resume:

    • Do not spawn further sub-agents until you read loop-budget.md on a subsequent run and verify that the human has increased your token cap.

© cobusgreyling, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/budget-negotiator of cobusgreyling/loop-engineering.

Open the folder on GitHubat commit f914d15

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in cobusgreyling/loop-engineering, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Budget Negotiator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Budget Negotiator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Budget Negotiator this skillcobusgreyling/loop-engineering11k1 repos~864Automated safety check: PassMIT
Long Horizon Promptingguanyang/open-agent-hub9771 repos~6.4kAutomated safety check: PassMIT
Agents Best PracticesDenisSergeevitch/agents-best-practices2.4k—~7.4kAutomated safety check: PassMIT
Context Compressionguanyang/open-agent-hub9772 repos~4.6kAutomated safety check: PassMIT
Amazon Bedrockaws/agent-toolkit-for-aws2.8k—~8.6kAutomated safety check: PassApache-2.0
Show Me Your Work Decision Logcursor/plugins11k8 repos~1.6kAutomated safety check: PassNone

Similar skills

  • Long Horizon Prompting

    guanyang/open-agent-hub

    This skill should be used when writing, enhancing, or evaluating the launch prompt for a long-running autonomous agent or a parallel multi-agent orchestration attacking a hard problem: pseudo-formal…

    977 GitHub starsUsed in 1 repo~6.4k tokens
    Agent WorkflowsAuto-check passed
  • Agents Best Practices

    DenisSergeevitch/agents-best-practices

    A skill your agent uses when designing, generating an MVP blueprint for, auditing, troubleshooting, refactoring, or explaining an agentic harness for any domain.

    2.4k GitHub stars~7.4k tokensUpdated 6 days ago
    AI & LLM EngineeringAuto-check passed
  • Context Compression

    guanyang/open-agent-hub

    This skill should be used when long-running agent sessions need context compression, structured summarization, compaction, token-per-task optimization, or durable handoff summaries that preserve…

    977 GitHub starsUsed in 2 repos~4.6k tokens
    AI & LLM EngineeringAuto-check passed
  • Amazon Bedrock

    aws/agent-toolkit-for-aws

    Official

    Builds generative AI applications on Amazon Bedrock. An agent skill from aws/agent-toolkit-for-aws.

    2.8k GitHub stars~8.6k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Official

    Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.

    11k GitHub starsUsed in 8 repos~1.6k tokens
    Agent WorkflowsAuto-check passed
  • Autoresearch Iteration Loop

    uditgoenka/autoresearch

    Runs an autonomous modify, verify, keep-or-discard loop against any metric, with subcommands for planning, debugging, fixing, security audits, shipping and more.

    6.5k GitHub starsUsed in 1 repo~2k tokens
    Agent WorkflowsAuto-check passed

More from cobusgreyling/loop-engineering

All 23 skills in this repo
  • Install Loop Engineering

    cobusgreyling/loop-engineering

    Installs Loop Engineering into a project through the single @cobusgreyling/loop CLI, scaffolding a report-only loop and a readiness score.

    11k GitHub starsUsed in 1 repo~648 tokens
    Auto-check passed
  • Loop Constraints Enforcer

    cobusgreyling/loop-engineering

    Loads a project's loop-constraints.md before any other action and blocks pushes, edits or merges that violate the rules it defines.

    11k GitHub starsUsed in 1 repo~475 tokens
    Auto-check: notes
  • Loop Change Verifier

    cobusgreyling/loop-engineering

    Acts as a skeptical checker for changes an implementer sub-agent made, running the tests, confirming the diff scope and returning approve, reject or escalate to a human.

    11k GitHub starsUsed in 1 repo~709 tokens
    Auto-check passed
  • Minimal Code Fix

    cobusgreyling/loop-engineering

    Makes the smallest code change that fixes one well-scoped problem, such as a CI failure, review comment or typo, without refactoring anything unrelated.

    11k GitHub starsUsed in 1 repo~671 tokens
    Auto-check: notes
  • Changelog Scan for Release Notes

    cobusgreyling/loop-engineering

    Scans merges to main since the last tag or date, extracting titles, labels and breaking-change or security signals as structured input for a release notes drafter.

    11k GitHub stars~779 tokensUpdated today
    Auto-check passed
  • CI Triage

    cobusgreyling/loop-engineering

    Parse CI failures, identify failing job/step, classify as flake, regression, env, or config.

    11k GitHub stars~517 tokensUpdated today
    Auto-check passed

Categories

Questions about Budget Negotiator

What does Budget Negotiator do?

An advanced skill for L3 autonomous loops. An agent skill from cobusgreyling/loop-engineering. Budget Negotiator is an agent skill from cobusgreyling/loop-engineering. An advanced skill for L3 autonomous loops.

When should I use Budget Negotiator?

Budget Negotiator fits situations like: tasks that involve Autonomous loops; tasks that involve LLM cost and token optimization.

How do I install Budget Negotiator in Claude Code?

Run `npx skills add cobusgreyling/loop-engineering --skill budget-negotiator -a claude-code`. Or copy the skill folder (skills/budget-negotiator in cobusgreyling/loop-engineering) into .claude/skills/budget-negotiator in your project. Claude Code loads it when a task matches its description.

How do I install Budget Negotiator in Codex?

Run `npx skills add cobusgreyling/loop-engineering --skill budget-negotiator -a codex`. Or copy the skill folder (skills/budget-negotiator in cobusgreyling/loop-engineering) into .agents/skills/budget-negotiator in your project. Codex loads it when a task matches its description.

Can I use Budget Negotiator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cobusgreyling/loop-engineering --skill budget-negotiator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/budget-negotiator, .gemini/skills/budget-negotiator, .github/skills/budget-negotiator and .opencode/skills/budget-negotiator in your project.

What does Budget Negotiator need to run?

SKILL.md names no scripts, command-line tools or credentials: Budget Negotiator is instructions for the agent only.

Does Budget Negotiator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Budget Negotiator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Budget Negotiator use?

Budget Negotiator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Budget Negotiator use?

About 864 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Budget Negotiator?

Skills that share tags, products or a category with Budget Negotiator: Long Horizon Prompting (guanyang/open-agent-hub, 977 stars), Agents Best Practices (DenisSergeevitch/agents-best-practices, 2.4k stars), Context Compression (guanyang/open-agent-hub, 977 stars) and Amazon Bedrock (aws/agent-toolkit-for-aws, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Budget Negotiator?

cobusgreyling (a GitHub user) maintains it in cobusgreyling/loop-engineering, which has 11,486 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 11, 2026.

Source: cobusgreyling/loop-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.