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 agentmods add commands/rahmanef63/control-room/vps-deploygit clone --depth 1 https://github.com/rahmanef63/control-roomWrote 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/commands/rahmanef63/control-room/vps-deploy)<a href="https://agentmods.dev/commands/rahmanef63/control-room/vps-deploy"><img src="https://agentmods.dev/badge/commands/rahmanef63/control-room/vps-deploy.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00797 |
| Opus 5 | $0.00000 | $0.00398 |
| Sonnet 5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade B, and why
vps-deploy scanned grade B with 2 findings 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 4d 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.
sudo usermod -aG docker "$USER" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://127.0.0.1:4000/api/health # frontend How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VPS Control Room — Deploy Workflow
Gunakan skill ini saat deploy, redeploy, atau troubleshoot systemd services.
Deploy Pertama Kali
# Set REPO_DIR to your actual repo path
REPO_DIR="<your-repo-path>"
cd "$REPO_DIR"
# 1. Install dependencies
bun install --cwd frontend
bun install --cwd agent
# 2. Setup env
cp .env.example .env.local
# Edit .env.local — isi semua secrets
# 3. Build
bun run --cwd frontend build
bun run --cwd agent build
# 4. Deploy Convex schema
bunx convex deploy
# 5. Setup permissions
sudo usermod -aG docker "$USER"
# Buat sudoers file
sudo tee /etc/sudoers.d/vps-control-room << 'SUDOERS'
# Replace <your-user> with your actual username
<your-user> ALL=(ALL) NOPASSWD: /usr/bin/systemctl restart vps-control-room-*
<your-user> ALL=(ALL) NOPASSWD: /usr/bin/fail2ban-client set sshd unbanip *
SUDOERS
sudo chmod 440 /etc/sudoers.d/vps-control-room
# 6. Install systemd units (auto-detects user and repo path)
sudo bash scripts/install-systemd.sh
# 7. Enable dan start
sudo systemctl enable --now vps-control-room-frontend
sudo systemctl enable --now vps-control-room-agent
Redeploy (Update Kode)
cd <your-repo-path>
git pull origin main
# Build ulang
bun install --cwd frontend && bun run --cwd frontend build
bun install --cwd agent && bun run --cwd agent build
# Deploy Convex (jika schema/functions berubah)
bunx convex deploy
# Restart services
sudo systemctl restart vps-control-room-frontend
sudo systemctl restart vps-control-room-agent
Atau jalankan: bash scripts/deploy.sh
Troubleshooting
# Cek status service
sudo systemctl status vps-control-room-frontend
sudo systemctl status vps-control-room-agent
# Lihat logs
sudo journalctl -u vps-control-room-frontend -f --no-pager
sudo journalctl -u vps-control-room-agent -f --no-pager
# Cek health endpoints
curl http://127.0.0.1:4000/api/health # frontend
curl http://127.0.0.1:4001/health # agent
# Restart manual jika perlu
sudo systemctl restart vps-control-room-frontend
sudo systemctl restart vps-control-room-agent
# Cek apakah port sudah listen
ss -tlnp | grep -E "4000|4001"
# Cek env loaded
sudo systemctl show vps-control-room-agent --property=Environment
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.
- 4d ago First seen · 116 lines · 0 tokens per session scan B 1f7345501714
vps-deploy is a command published in the GitHub repository rahmanef63/control-room (19 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 797 tokens. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
portaljs-architect
Recommend a data-portal architecture (storage, compute, catalog, access, hosting, metadata) from your needs, then hand off to the build skills. The advisory entry point.
portaljs-check-data-quality
Audit a local or remote tabular file (CSV/TSV) for common data quality issues. Read-only. Use only when the user explicitly asks to check or audit data quality.
upgrade-webkit
Upgrade Bun's WebKit fork to the latest upstream version of WebKit.
dedupe
Find duplicate GitHub issues.
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).
start
Runs a project that has already been compiled with vendure build.