Tool-Call Budget Guard
Plan and enforce explicit limits around a tool-calling workflow.
Get a budget ledger, stopping condition and graceful partial-result plan.
Free · 2 KB · SKILL.md, instructions and example files. Provide tool names, per-call cost assumptions and the allowed total budget.
A worked example
A small example to try before using your own data.
Input
{
"unit": "calls",
"limit": 3,
"used": 2,
"requested_calls": 2
}Expected result
{
"decision": "deny batch",
"remaining": 1,
"alternative": "Run at most one authorized call, or return the current partial result. Do not increase the cap."
}What to check: No more than one additional call may run. A batch must be reserved before dispatch, not checked after it spends the budget.
Limits: This recipe is an integration contract, not a built-in billing control. An actual tool dispatcher must enforce the ledger atomically.
Worked example included. Model-specific performance and vendor compatibility have not been benchmarked.
🧠 Why it works
No more than one additional call may run. A batch must be reserved before dispatch, not checked after it spends the budget.
⚙️ How it works
- Represent budget units explicitly: calls, tokens, money or elapsed time are not interchangeable.
- Reserve budget for the next operation before dispatch and deny operations that exceed the remaining allowance.
- Reconcile known actual cost after the call and keep failed/unknown-cost calls visible.
- Define the useful partial result to return when a limit is reached; never silently raise the cap.
- Test the boundary case where remaining budget equals one call and the case where it is insufficient.
Description
Get a budget ledger, stopping condition and graceful partial-result plan.
Provide tool names, per-call cost assumptions and the allowed total budget.
Limits: This recipe is an integration contract, not a built-in billing control. An actual tool dispatcher must enforce the ledger atomically.
Recommended Use
Sign in to suggestTools and workflow packs this skill pairs well with. Forge picks are auto-generated from category + capability signals; Community picks are added by people who've used the pairing.
No matches yet. Be the first to suggest a pairing, or the Forge will populate suggestions as signals align.
Report compatibility
Tell the community which tool you used this skill with, and whether it worked.
Suggest a pairing
Recommend a tool or workflow pack that this skill works well with. Up to 5 recommendations per day.