/omh-spend-gate

name: "omh-spend-gate"
description: "[omh] Spending money on the user's behalf -- a card checkout, an HTTP 402 or pay-per-request call, a wallet transfer, a booking, a paid data endpoint: show a pre-spend card (payee, total with fees, cap, refund terms, approver) first, and call it done only on an observed receipt. Use when the user says: spend-gate, spend gate, pre-spend, pre-spend card, spend cap, spending cap, spend limit, spending limit."
license: MIT
author: "oh-my-hermes maintainers"
metadata:
  hermes:
    tags: [workflow, oh-my-hermes, spend-control]
    category: spend-control
    phase: pre-spend
    role: guide
    quality_tier: receipt-gated-spend
    related_skills: [omh-browser, omh-feedback-triage, omh-finance-analysis, omh-provider-profile-posture]

Spend Gate

This is a Hermes-native `spend-gate` workflow skill.

Why This Exists

`spend-gate` exists because money movement had at most one native guard, on one rail: where Hermes' saved-card fill is present it asks before filling a card and refuses when nobody can confirm, while an HTTP 402 call, a wallet transfer, a booking, or a paid data endpoint had no pre-spend check, no receipt rule, and no cap. `omh-browser` gates payment only inside a page, and `omh-provider-profile-posture` claims no payment at all.

First Steps

• Check that a person can answer in this session; in a scheduled, webhook, API-server, single-query, background-worker, or subagent run, prepare the card and stop before any payment surface.
• Read the quote from its source and fill the pre-spend card from it, the cap included, before anything is submitted.

Do Not Use When

• The page task moves no money -- open a URL, log in, fill a form, capture blockers; use `omh-browser`.
• Users report a payment failure in the product and the ask is to sort those reports; use `omh-feedback-triage`.
• The ask is budget vs actual, a budget variance, or the month-end close; use `omh-finance-analysis`.
• The ask is a provider profile's posture or whether its secrets are present, with nothing bought; use `omh-provider-profile-posture`.

Examples

Good example:

• Prompt: the api answered 402 payment required, pay it so we get the dataset
• Expected behavior: Read the amount, currency, payee, and method from the 402 challenge, show pre_spend_card/v1 with the cap and what remains of it, wait for the person's typed yes, pay through the client they installed, and report done only with the receipt header and the amount charged.
• Why: A 402 call spends the moment it is retried with a credential; the card is the one point where the person sees the price.

Bad example:

• Prompt: the checkout timed out, just click pay again
• Expected behavior: Mark the first charge unknown, look for it in the order history or the card activity, and show a new card only once it is shown absent.
• Why: A second click after a success nobody saw is a double charge.

Completion Checklist

• The pre-spend card names payee, item, total with fees and currency, rail, cap, refund terms, reversibility, and approver.
• The person's typed confirmation in this session matches the card, and a host prompt's answer, when one appeared, sits beside it.
• The spend is called done only with an observed order id, transaction id, or receipt header and the amount charged.
• An unknown outcome was reconciled before any retry, or is reported as unknown.
• The cap ledger holds metadata only, and OMH moved no money and held no credential.

Recovery Notes

• If the total changed between the card and the payment step, stop, show a new card, and ask again.
• If no receipt can be observed, report the spend as submitted or unknown, never as complete.

Workflow Lane

• Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `live-incident-response`, `automation-blueprint`, `github-event-ops`, `github-issue-intake`, `buzz`, `+40 more`) - schedules, status, health, and ops review.
• If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
• Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.

When to Use

Use before the agent moves money on any rail: a card checkout in the browser, an HTTP 402 or pay-per-request call, a wallet transfer, a booking or deposit, a paid data endpoint, or a renewal that charges again. The output is a pre-spend card the person confirms, the receipt that proves the charge, and a metadata-only ledger against their cap; OMH moves no money, holds no credential, and never spends from a run nobody can answer.

Strong routing signals: `spend-gate`, `spend gate`, `pre-spend`, `pre-spend card`, `spend cap`, `spending cap`, `spend limit`, `spending limit`, `spend request`, `spend approval`, `approve the spend`, `approve this purchase`, `approve the purchase`, `complete the purchase`, `complete the checkout`, `buy this for me`, `buy it for me`, `place the order`, `place an order`, `pay with my card`, `pay with my saved card`, `with my saved card`, `with my card`, `with my credit card`, `use my card`, `use my credit card`, `send money`, `pay again`, `click pay again`, `http 402`, `402 payment required`, `402 challenge`, `pay per request`, `pay-per-request`, `paid endpoint`, `paid data endpoint`, `wallet transfer`, `from my wallet`, `money on my behalf`, `spend on my behalf`, `pay on my behalf`, `buy on my behalf`, `retry the payment`, `retry the purchase`, `retry the charge`, `did the payment go through`, `did the charge go through`, `pay for the booking`, `결제`, `송금`, `이체`, `입금`, `지불`, `납부`, `구매`, `구입`, `주문`, `예매`, `사줘`, `사 줘`, `사주세요`, `사 주세요`, `충전`, `예약`, `구독`, `갱신`, `후원`, `기부`, `보내`, `카드로`, `지갑에서`, `계좌에서`

Catalog Metadata

Category: `spend-control` Phase: `pre-spend` Hermes role: `guide` Quality tier: `receipt-gated-spend` Reasoning demand: `standard`

Quality bar:

• Read the payee, the total, and the currency