Learn About Omd

Step 2: Analyze Agent Usage (if token data exists)

if [[ "$HAS_TOKENS" == "true" ]]; then
  echo ""
  echo "TOP AGENTS BY USAGE:"
  cat "$TOKEN_FILE" | jq -r '.agentName // "main"' | sort | uniq -c | sort -rn | head -10

  echo ""
  echo "MODEL DISTRIBUTION:"
  cat "$TOKEN_FILE" | jq -r '.modelName' | sort | uniq -c | sort -rn
fi

Step 3: Generate Recommendations

Based on patterns found, output recommendations:

If high Opus usage (>40%) and no ecomode:

• "Consider using ecomode for routine tasks to save tokens"

If no pipeline usage:

• "Try /pipeline for code review workflows"

If no security-reviewer usage:

• "Use security-reviewer after auth/API changes"

If defaultExecutionMode not set:

• "Set defaultExecutionMode in /omd-setup for consistent behavior"

Step 4: Output Report

Format a nice summary with:

• Token summary (total, by model)
• Top agents used
• Underutilized features
• Personalized recommendations

Graceful Degradation

If no data found:

📊 Limited Usage Data Available

No token tracking found. To enable tracking:
1. Ensure ~/.omd/state/ directory exists
2. Run any OMC command to start tracking

Tip: Run /omd-setup to configure OMC properly.

Example Output

📊 Your OMC Usage Analysis

TOKEN SUMMARY:
- Total records: 1,234
- By Model: opus 45%, sonnet 40%, haiku 15%

TOP AGENTS:
1. executor (234 uses)
2. architect (89 uses)
3. explore (67 uses)

UNDERUTILIZED FEATURES:
- ecomode: 0 uses (could save ~30% on routine tasks)
- pipeline: 0 uses (great for review workflows)

RECOMMENDATIONS:
1. Set defaultExecutionMode: "ecomode" to save tokens
2. Try /pipeline review for PR reviews
3. Use explore agent before architect to save context