$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-live-cost-budget-action-guardGate live financial authority actions — budget threshold changes, Savings Plan purchases, and Reserved Instance commitments. These are committed spend or can trigger immediate service suspension.
| 1 | # Alibaba Cloud Live Cost Budget Action Guard |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Act as the guarded live Alibaba Cloud operator for alibaba-live-cost-budget-action-guard work. Gate every budget threshold change, Savings Plan purchase, and Reserved Instance commitment with a full financial-impact assessment and explicit financial-authority approval. Treat Savings Plan and RI purchases as the highest-risk financial actions — they are non-refundable committed spend contracts. |
| 6 | |
| 7 | ## When to Use |
| 8 | |
| 9 | Use this skill when: |
| 10 | |
| 11 | - A Cost Manager budget alert threshold needs to be increased or decreased |
| 12 | - A Savings Plan purchase (compute-based or ECS-instance) is being requested |
| 13 | - A Reserved Instance commitment (zone or regional, 1-year or 3-year) is being submitted |
| 14 | - An operator needs to audit current budgets, alert thresholds, and active commitments |
| 15 | - A budget anomaly or unexpected billing spike needs investigation and remediation |
| 16 | |
| 17 | ## When NOT to Use |
| 18 | |
| 19 | Do not use this skill when: |
| 20 | |
| 21 | - The task is a read-only cost report review with no billing mutation intent |
| 22 | - The task involves resource rightsizing or scheduling that does not touch billing account settings |
| 23 | - The task is unrelated to Alibaba Cloud billing, Savings Plans, or Reserved Instances |
| 24 | |
| 25 | ## Key Risk Facts |
| 26 | |
| 27 | - **Savings Plans** are non-refundable committed spend contracts (hourly commitment × term). A compute-based Savings Plan requires an hourly CNY/USD commitment for 1 or 3 years — there is no cancellation. |
| 28 | - **Reserved Instances** lock capacity for 1 or 3 years. Partial/all-upfront payment options exist. RI purchases cannot be refunded. |
| 29 | - **Budget threshold reduction below current spend** triggers immediate service suspension in Alibaba Cloud BSS. Services are suspended within minutes of the billing threshold being breached. Restoration requires manual re-enabling of suspended services and can cause data loss in stateful workloads. |
| 30 | - **All three actions** require the 6-step live-guard gate: (1) identity confirm, (2) current inventory capture, (3) blast radius assessment, (4) financial authority confirm, (5) explicit written approval, (6) post-action verification. |
| 31 | |
| 32 | ## Pre-Flight Checklist |
| 33 | |
| 34 | Before executing any billing mutation, verify all of the following: |
| 35 | |
| 36 | 1. **Account identity confirmed** — confirm the BSS account ID, billing account name, and the operator's RAM identity. |
| 37 | 2. **Current budget inventory captured** — list all active budgets, current thresholds, alert notification targets, and actual spend vs. threshold ratio before any change. |
| 38 | 3. **Commitment inventory captured** — list all active Savings Plans (commitment amount, remaining term) and Reserved Instances (instance type, scope, expiry) before any new purchase. |
| 39 | 4. **Utilization verified** — for Savings Plans and RIs: confirm current utilization rate of existing commitments before purchasing additional. Purchasing new commitments when existing ones are underutilized compounds waste. |
| 40 | 5. **Blast radius assessed** — for budget threshold reduction: calculate the gap between the proposed threshold and current spend. Confirm the new threshold is above the minimum operational spend. Document which services are at risk of suspension. |
| 41 | 6. **Financial authority confirmed** — the approver must have explicit financial authority (BSS account administrator, VP Engineering, CFO delegate, or equivalent). Document their identity and written approval. |
| 42 | |
| 43 | ## Required Confirmation |
| 44 | |
| 45 | The operator must explicitly state all of the following before any mutation is executed: |
| 46 | |
| 47 | - "I confirm the BSS account is `<ACCOUNT_ID>` and the operator identity is `<RAM_IDENTITY>`." |
| 48 | - "I have reviewed the current budget and commitment inventory and the proposed change is `<SPECIFIC_CHANGE>`." |
| 49 | - "I have verified the current utilization of existing commitments is `<RATE>%`." |
| 50 | - "I have assessed the blast radius: `<DESCRIPTION>`." |
| 51 | - "I have financial authority for this change (or I confirm that `<APPROVER_NAME>` has provided written approval)." |
| 52 | - "I approve this billing/commitment action." |
| 53 | - For Savings Plan purchase: "I understand this is a `<1/3>`-year non-refundable commitment of approximately `<AMOUNT>` per hour and I approve the purchase." |
| 54 | - For RI purchase: "I understand this is a `<1/3>`-year non-refundable commitment for `<INSTANCE_TYPE>` in `<REGION/ZONE>` and I approve the purchase." |
| 55 | |
| 56 | ## Execution Steps |
| 57 | |
| 58 | 1. Capture pre-change billing state: budget list, Savings Plan inventory, RI inventory. |
| 59 | 2. Confirm active operator has BSS administrator permissions. |
| 60 | 3. Present the planned action, financial impact estimate, and current inventory to the operator for explicit approval. |
| 61 | 4. Execute the m |