What problem does it solve?
Budget limits stated in a prompt are advisory and can be forgotten or overridden mid-session. This Skill makes DoorDash spending limits deterministic by routing every cart mutation and checkout through an audited wrapper script that prices the cart, checks a persistent policy, and refuses out-of-policy orders with a machine exit code.
Core Features & Use Cases
- Deterministic Policy Enforcement: Per-order, daily, weekly, and monthly caps plus cooldown periods and allowed ordering hours, all checked against a persistent JSONL spend ledger before any checkout URL is issued.
- Bypass Protection: Pairs with a PreToolUse hook that denies raw dd-cli checkout and cart-add calls that try to skip the wrapper, and blocks by default when the cart subtotal cannot be parsed.
- Spend Reporting and Reconciliation: The status subcommand reports spend-to-date versus each cap, and the companion /doordash-budget command reconciles ledger intents against dd-cli order history as paid or abandoned.
- Use Case: An agent building a DoorDash cart with dd-cli calls dd-guard checkout, which prices the cart, finds the 24-hour total would exceed the daily cap, exits with code 2, and the agent relays the exact reason instead of completing the purchase.
Quick Start
Ask the agent to check your remaining DoorDash budget and then build a cart, and it will route all cart changes and checkout through the dd-guard wrapper automatically.
