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 KhaledSaeed18/dotclaude --skill vps-ops-toolkitgit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/vps-ops-toolkit)<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/vps-ops-toolkit"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/vps-ops-toolkit/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/khaledsaeed18/dotclaude/vps-ops-toolkit"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/vps-ops-toolkit.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.00053 | $0.01031 |
| Opus 5.5 | $0.00021 | $0.00412 |
| Sonnet 5.5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade B, and why
vps-ops-toolkit scanned grade B 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| `ship.sh` | tar the folder over SSH and run the installer with sudo | How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A server is operated when something other than a person notices a problem and when the database can be rebuilt from a copy that was proven to restore. The toolkit lives in the API repository under ops/, is installed by one command, and reports through a webhook only when the set of problems changes.
Hard rules: never break these
- Installing or changing cron, logrotate or anything under
/etcis a production action. The owner authorisesship.sh; you prepare and review it. - A backup that was not restored is not a backup. Keep only archives whose restore fingerprint matched the source snapshot. Nothing is kept from a failed run.
- The server holds only the public encryption key. The private key stays with the owner, offline; a compromised server cannot read old backups.
- Alerts only on change. Every run logs; the webhook fires when a problem appears, persists with a change, or resolves. No heartbeat spam.
- Never store webhook URLs or keys in the repository. They live in
/etc/<prefix>-*.env, mode 600, created once from the examples and never overwritten by the installer.
Step 1: Fit the templates to the project
Copy templates/ops/ into the repository as ops/ and rename the app prefix (app-ops, app-health, app-backup) to the project's name in install.sh, the cron files, the logrotate file and the env examples. The files:
| File | Role |
|---|---|
lib/alert.sh |
one Discord embed per alert, colour by severity, fields, length limits |
health/health-check.sh |
services, Coolify resources by label, capacity, backup age, certificate verification per domain, readiness, pending reboot; state in /var/lib, alert on change |
backup/backup.sh with snapshot.sql and fingerprint.sql |
one-snapshot pg_dump plus roles, restore into a throwaway Postgres with no network, fingerprint diff, age encryption, local and optional git offsite retention |
install.sh |
idempotent root installer: scripts, schedules, logrotate, env files created only when missing, a pre-deploy backup profile, one health run |
ship.sh |
tar the folder over SSH and run the installer with sudo |
What ships with it
12 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.
- templates/ops/backup/backup.cron 227 B
- templates/ops/backup/backup.env.example 655 B
- templates/ops/backup/backup.sh 6.8 KB runs code
- templates/ops/backup/fingerprint.sql 627 B
- templates/ops/backup/snapshot.sql 505 B
- templates/ops/health/health-check.cron 224 B
- templates/ops/health/health-check.sh 8.4 KB runs code
- templates/ops/health/health.env.example 714 B
- templates/ops/health/ops.logrotate 218 B
- templates/ops/install.sh 2.3 KB runs code
- templates/ops/lib/alert.sh 2.0 KB runs code
- templates/ops/ship.sh 510 B runs code
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 · 49 lines · 53 tokens per session scan B f4d8f7e95745
vps-ops-toolkit is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 1,031 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-05.
Other skills, from other repositories
cost-optimization
Audit and reduce infrastructure and tooling costs without sacrificing reliability or velocity. Use this skill when reviewing monthly cloud or SaaS spend, finding unused resources, rightsizing infrastructure, negotiating vendor contracts, deciding what to consolidate, or planning for budget cuts. Triggers on cost…
monitoring-and-alerting
Design and run a monitoring system for a website or web app. Use this skill when setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue. Triggers on monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert…
launch-runbook
Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers…
netlify-development
Best practices for building and deploying Netlify sites, covering serverless and edge functions, Netlify Blobs storage, the Image CDN, and build configuration. Use when writing Netlify Functions or Edge Functions, configuring netlify.toml or redirects/headers, managing environment variables across deploy contexts…
agents-v2-py
Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
cloudflare-development
Cloudflare Workers, Pages, KV, D1, R2, and Durable Objects development best practices for edge computing applications.