Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add kevinnft/ai-agent-skills --skill vps-cleanupgit clone --depth 1 https://github.com/kevinnft/ai-agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kevinnft/ai-agent-skills/vps-cleanup)<a href="https://agentmods.dev/skills/kevinnft/ai-agent-skills/vps-cleanup"><img src="https://agentmods.dev/badge/skills/kevinnft/ai-agent-skills/vps-cleanup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kevinnft/ai-agent-skills/vps-cleanup"><img src="https://agentmods.dev/badge/skills/kevinnft/ai-agent-skills/vps-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00027 | $0.03832 |
| Opus 5 | $0.00014 | $0.01916 |
| Sonnet 5 | $0.00005 | $0.00766 |
| Haiku 4.5 | $0.00003 | $0.00383 |
Grade C, and why
vps-cleanup scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/temp-workspace/ How it starts
The opening of the file, as written. The whole thing — 527 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VPS Cleanup
Systematic approach to cleaning up VPS disk space — analyze files, categorize by importance, safely delete temporary/old data without losing critical files.
When to Use
- User asks "apa yang gak penting?" or "what can I delete?"
- Disk space running low (> 80% used)
- Home directory cluttered with temporary files
- After completing projects (cleanup workspace)
Workflow
Phase 1: Analyze Current State
# Check disk usage
df -h /
# Analyze home directory
cd /home/ubuntu
du -sh * 2>/dev/null | sort -h
# Check large directories
du -h --max-depth=1 | sort -h | tail -20
Phase 2: Categorize Files
For each file/directory, assess:
| Category | Keep? | Examples |
|---|---|---|
| Backups | ✅ Keep | *.zip, *.tar.gz with "backup" in name |
| System | ✅ Keep | snap/, .cache/, .local/ |
| Active projects | ✅ Keep | Current development work |
| Temporary workspaces | ❌ Delete | Analysis folders, test directories |
| Old archives | ❌ Delete | Extracted folders + their .tar.gz (duplicates) |
| Generated outputs | 🟡 Optional | PNGs, reports (if source exists) |
| Source files | 🟡 Optional | .html if .png generated, .drawio if exported |
Phase 3: Build Decision Matrix
Create analysis table:
files = {
'file.zip': {
'size': '135M',
'type': 'backup',
'keep': True,
'reason': 'Important backup'
},
'temp-workspace/': {
'size': '538M',
'type': 'workspace',
'keep': False,
'reason': 'Temporary analysis, reports done'
},
# ... more files
}
Calculate:
- Total size
- Deletable size
- Keep size
- Percentage reclaimable
Phase 4: Present Analysis
Show user:
- Summary stats (total, keep, delete, %)
- Keep list (sorted by size, with reasons)
- Delete list (sorted by size, with reasons)
- Recommendations (phased approach)
Format:
✅ KEEP (IMPORTANT)
135M backup.zip Important backup
2.4M snap/ System directory
❌ CAN DELETE (NOT IMPORTANT)
538M temp-workspace/ Temporary, work done
1.2M diagrams/ PNGs generated
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 527 lines · 27 tokens per session scan C 80c53d84d40e
vps-cleanup is a skill published in the GitHub repository kevinnft/ai-agent-skills (14 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 3,832 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
absolute-prune
Dead code and dependency cleanup, repo-wide: unused deps, unreferenced exports, unreachable code, orphaned files — removed only with tool evidence, in reversible waves. Runs on green main. For diff-scoped cleanup use absolute-simplify. Triggers on "absolute prune", "remove dead code", "find unused deps/exports", "what…
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
extract-design
Extract a complete design system — colors, typography, spacing, components, shadows, and W3C design tokens — from any live website using Dembrandt. Runs a headless browser against the URL and returns real computed values from the DOM. Use when you need a site's actual design tokens, want to reverse-engineer a visual…
elevation-and-depth
Elevation — subtle shadows and layering — communicates visual hierarchy by lifting elements above the surface. Combined with border-radius, it creates the tactile quality of cards, modals, and interactive surfaces. Use when designing cards, dropdowns, modals, tooltips, or any floating UI element.
loading-states-and-perceived-performance
Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…
tab-navigation
Tabs organise related content under a shared context — switching tabs swaps the view without leaving the page. Use when a screen has multiple distinct content areas that share a common header or action set, and when the user needs to switch between them frequently. Use when designing tabbed layouts, content panels…