agentleFS
huiferhuifer/CloudSaver/skills/cost-monitor/SKILL.md

cost-monitor

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Cloud service cost monitoring expert. Sets up alerts, analyzes trends, and predicts future costs. Trigger when user mentions cost monitoring, usage alerts, or cost forecasting.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. TH3H4RM1N4T0R/claude-code-cost-monitor★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

Files
SKILL.md

Cloud Cost Monitoring Expert

Monitoring Components

ComponentPurposeFrequency
Usage MetricsTrack current usageReal-time
AlertsEarly warningOn threshold
TrendsPattern analysisDaily/Weekly
ForecastingCost predictionMonthly

Audit Workflow

Step 1: Set Up Alerts

Configure threshold-based notifications for each service. See cases/alert-setup.md for implementation.

Step 2: Collect Historical Data

Store usage metrics over time for analysis.

Step 3: Analyze Trends

Identify patterns and growth rates. See cases/trend-analysis.md for detailed analysis.

Step 4: Generate Forecasts

Predict future costs based on historical data.

Matching Cases

TaskCase FileOutput
Alert setupcases/alert-setup.mdNotification config
Trend analysiscases/trend-analysis.mdGrowth patterns
Anomaly detectioncases/trend-analysis.mdSpike alerts

Service-Specific Monitoring

Supabase

-- Database size
SELECT pg_database_size(current_database());

-- Active connections
SELECT count(*) FROM pg_stat_activity;

-- Query performance
SELECT query, calls, total_exec_time 
FROM pg_stat_statements 
ORDER BY total_exec_time DESC LIMIT 10;

Cloudflare

# Workers usage
wrangler analytics

# D1 usage
wrangler d1 info <database>

Redis

# Memory usage
redis-cli INFO memory

# Key count
redis-cli DBSIZE

Output Format

## Cost Monitoring Report

### 1. Current Usage
| Service | Metric | Value | Threshold | Status |
|---------|--------|-------|-----------|--------|
| Supabase | DB Size | X MB | 400 MB | OK |
| Workers | Requests | X K | 80 K | Warning |

### 2. Trend Analysis (30 days)
| Service | Metric | Daily Growth | Projected (30d) |
|---------|--------|--------------|-----------------|
| Supabase | DB Size | X MB/day | X MB |

### 3. Alerts Configured
- [Service] [Metric]: [Threshold] → [Channel]

### 4. Recommendations
1. [Action] → Expected impact

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.