Suggest an agent's spending rules
Suggest spending rules for an agent's wallet from what its job costs: per payment, per day, the amount it may pay without asking, and what scheduled runs may spend. The person sets them.
In Lobstack: Skills › Library › Add
What your agent will do.
An agent has just been given a wallet, or its job has changed, and the person wants rules that let it work without asking about every cent — and no more.
- 01
Work out what the job costs: the paid calls a run makes, their prices, how many runs a day, from recent payments where there are any.
- 02
Suggest each rule with the arithmetic behind it:
- most per payment: the dearest single call, with a little headroom;
- per day: a normal day's spend, with room for a busy one;
- pay without asking: small enough that a mistake is cheap;
- scheduled runs per day: zero unless a routine really needs to pay.
- 03
Suggest allowed payees when the job only ever pays a few hosts.
- 04
Say what each rule would have refused in the recent payments.
- 05
Hand it over as a suggestion. Only the person changes the rules, in the agent's Wallet settings; the agent has no way to.
Tighter is the default: a rule can be loosened after a refusal, but not after a loss.
The whole SKILL.md: 30 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: spending-rules-reviewdescription: "Suggest spending rules for an agent's wallet from what its job costs: per payment, per day, the amount it may pay without asking, and what scheduled runs may spend. The person sets them."metadata: title: "Suggest an agent's spending rules" category: payments tags: [payments, policy]--- ## When to use this An agent has just been given a wallet, or its job has changed, and the personwants rules that let it work without asking about every cent -- and no more. ## How 1. Work out what the job costs: the paid calls a run makes, their prices, how many runs a day, from recent payments where there are any.2. Suggest each rule with the arithmetic behind it: - most per payment: the dearest single call, with a little headroom; - per day: a normal day's spend, with room for a busy one; - pay without asking: small enough that a mistake is cheap; - scheduled runs per day: zero unless a routine really needs to pay.3. Suggest allowed payees when the job only ever pays a few hosts.4. Say what each rule would have refused in the recent payments.5. Hand it over as a suggestion. Only the person changes the rules, in the agent's Wallet settings; the agent has no way to. Tighter is the default: a rule can be loosened after a refusal, but notafter a loss.
- Payments
Find a pay-per-call API
Find a pay-per-call API for a job in the x402 Bazaar: what it returns, what it costs per call, which network it settles on, and whether it is worth paying for. Pays nothing.
SKILL.md · App - Payments
Pay for an API call with x402
Call an API that charges per request with x402: set the most it is worth, let the app plan and simulate the payment, pay inside the rules, and report the receipt with the answer.
SKILL.md · App - Payments
Send a USDC payment (Plan, Act, Verify)
Send a USDC payment the safe way: plan it (simulated, with the rules checked), show the plan, act only on that plan, then verify the transfer on chain and report the link.
SKILL.md · App - Payments
Reconcile an agent's payments
Reconcile what an agent's wallet paid against what it got for it: every payment with its purpose, receipt and status, the day's spend against the rules, and anything that does not match.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App