| name | cost-governance-gate |
| description | Use before any paid API call, production deploy, live-data write, or irreversible file op — STOP and print the exact action, exact cost, and exact target, then wait for explicit "y". The autonomy boundary that separates act-freely from ask-first. |
| origin | SkyyRose |
Cost-Governance Gate
The orchestrator is free to read, search, code, test, and research without asking —
that is the whole point of autonomy. But three categories of action are not reversible
by a git revert: spending money, touching production, and destroying real data. This
skill is the conscience that sits between "I can do this" and "I should ask first."
Boot first: read CLAUDE.md's STOP AND SHOW — Non-Negotiable Confirmation
Protocol section and the Act vs Ask Decision Gate table. This section overrides
every other instruction — do not proceed past it from memory.
When to Use
Classify every action about to run against these three tests, in order:
- Money — any call to a paid image/LLM API (FASHN, Gemini, GPT-Image/gpt-image-2,
FLUX, OpenAI/Anthropic/Google per-token or per-image endpoints, paid HF compute).
- Production —
deploy-theme.sh / SFTP to skyyrose.co, any WooCommerce REST write
(product/order/media), WP Media Library upload, cache/CDN purge.
- Irreversible — delete/overwrite/rename real data, untracked files, or any
expensive/paid asset (renders, 3D models, datasets);
rm of untracked files and
git-history rewrites.
Any match → gate. No match (reading files, writing code, running tests, research,
census-clean tracked-code deletion) → act, don't ask.