spend-cap-manager
Skill2 starsChanged 5 months agoApache-2.0View on GitHub
Cloud service spend cap and budget management expert. Configures spending limits, sets up budget alerts, and implements cost controls. Trigger when user mentions spend cap, budget limits, or cost control.
In this repository8 other files it gives its agents.
- cloudflare-auditSkill
- cost-audit-masterSkill
- cost-monitorSkill
- d1-cost-optimizerSkill
- index-optimizerSkill
- query-rewriterSkill
- redis-auditSkill
- supabase-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Verify usage against free tier limits for each service.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Spend Cap & Budget Management Expert
Service Limits
| Service | Free Tier | Spend Cap | Budget Control |
| Supabase | Yes | Built-in | Dashboard |
| Cloudflare | Yes | Manual | Workers/KV |
| Redis | Varies | Provider | Provider |
| Vercel | Yes | Built-in | Dashboard |
| Netlify | Yes | Built-in | Dashboard |
Audit Workflow
Step 1: Check Current Usage
Verify usage against free tier limits for each service.
Step 2: Configure Spend Caps
Enable built-in spend caps where available.
See cases/supabase-spend-cap.md for Supabase configuration.
Step 3: Implement Budget Controls
For services without built-in caps, implement custom controls.
See cases/cloudflare-budget.md for Workers/KV budget control.
Step 4: Set Up Alerts
Configure notifications before hitting limits.
Matching Cases
| Service | Case File | Control Type |
| Supabase | cases/supabase-spend-cap.md | Built-in cap |
| Cloudflare | cases/cloudflare-budget.md | Custom budget |
Threshold Recommendations
| Service | Warning | Critical | Action |
| Supabase DB | 70% | 90% | Enable cap |
| Supabase Storage | 70% | 90% | Enable cap |
| Workers requests | 70% | 90% | Rate limit |
| D1 Row Reads | 70% | 90% | Query cache |
| KV operations | 70% | 90% | Local cache |
Output Format
## Spend Cap Management Report
### 1. Current Status
| Service | Usage | Limit | Status | Spend Cap |
|---------|-------|-------|--------|-----------|
| Supabase DB | X MB | 500 MB | X% | Enabled |
| Workers | X K | 100 K | X% | Manual |
### 2. Recommendations
1. [Service]: Enable spend cap / Set budget limit
2. [Service]: Set alert at X% threshold
### 3. Implementation
Reference: cases/<case-name>.mdDoes 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
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.