feat: Add OCI awareness across agents and skills

Adds awareness of Oracle Cloud Infrastructure to any plugin that referenced
at least two of the major cloud vendors already. Skills updated to include
OCI services. Also updated some of the other cloud references.

Signed-off-by: Avi Miller <me@dje.li>

plugins/cloud-infrastructure/skills/cost-optimization/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: cost-optimization
-description: Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
+description: Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
 ---
 
 # Cloud Cost Optimization
 
-Strategies and patterns for optimizing cloud costs across AWS, Azure, and GCP.
+Strategies and patterns for optimizing cloud costs across AWS, Azure, GCP, and OCI.
 
 ## Purpose
 
@@ -149,6 +149,26 @@ resource "aws_s3_bucket_lifecycle_configuration" "example" {
 - 24-hour maximum runtime
 - Best for batch workloads
 
+## OCI Cost Optimization
+
+### Flexible Shapes
+
+- Scale OCPUs and memory independently
+- Match instance sizing to workload demand
+- Reduce wasted capacity from fixed VM shapes
+
+### Commitments and Budgets
+
+- Use annual commitments for predictable spend
+- Set compartment-level budgets with alerts
+- Track monthly forecasts with OCI Cost Analysis
+
+### Preemptible Capacity
+
+- Use preemptible instances for batch and ephemeral workloads
+- Keep interruption-tolerant autoscaling groups
+- Mix with standard capacity for critical services
+
 ## Tagging Strategy
 
 ### AWS Tagging
@@ -208,6 +228,7 @@ resource "aws_budgets_budget" "monthly" {
 - AWS Cost Anomaly Detection
 - Azure Cost Management alerts
 - GCP Budget alerts
+- OCI Budgets and Cost Analysis
 
 ## Architecture Patterns
 
@@ -282,6 +303,7 @@ resource "aws_cloudwatch_metric_alarm" "cpu_high" {
 - **AWS:** Cost Explorer, Cost Anomaly Detection, Compute Optimizer
 - **Azure:** Cost Management, Advisor
 - **GCP:** Cost Management, Recommender
+- **OCI:** Cost Analysis, Budgets, Cloud Advisor
 - **Multi-cloud:** CloudHealth, Cloudability, Kubecost
 
 

plugins/cloud-infrastructure/skills/cost-optimization/references/tagging-standards.md

@@ -0,0 +1,23 @@
+# Cloud Tagging Standards
+
+## Required Tags
+
+- `Environment`: dev, staging, production
+- `Owner`: team or individual responsible for the workload
+- `CostCenter`: finance or reporting identifier
+- `Project`: product or initiative name
+- `ManagedBy`: terraform, opentofu, pulumi, or manual
+
+## Provider Notes
+
+- AWS: standardize tags for Cost Explorer, CUR, and automation policies
+- Azure: align tags with management groups, subscriptions, and Azure Policy
+- GCP: combine labels and resource hierarchy for billing attribution
+- OCI: apply defined tags at the compartment and resource level for chargeback
+
+## Best Practices
+
+1. Publish an approved tag dictionary and naming rules.
+2. Enforce tags with policy and CI validation.
+3. Inherit tags from shared modules whenever possible.
+4. Audit for missing or inconsistent tags weekly.