Borrowing it
Nothing to install: this file belongs to rahmanef63/control-room. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rahmanef63/control-room/main/.claude/commands/vps-control-room.mdgit 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-control-room)<a href="https://agentmods.dev/commands/rahmanef63/control-room/vps-control-room"><img src="https://agentmods.dev/badge/commands/rahmanef63/control-room/vps-control-room.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.1 | $0.00000 | $0.00511 |
| Opus 5 | $0.00000 | $0.00255 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
vps-control-room scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS http://127.0.0.1:4000/api/health How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VPS Control Room — Project Playbook
Use this command for project-level runtime/deploy troubleshooting. Root CLAUDE.md is the architecture SSOT; this file only adds a short operational checklist.
Invariants
- Frontend:
<repo>/frontend— SvelteKit 2 + Svelte 5, adapter-node on Node 22 in production; Bun is tooling. - Agent:
<repo>/agent— Node 22 + node-pty; host access stays here. - Browser terminal output: SSE from SvelteKit; frontend server bridges to the agent WebSocket.
- Production frontend service:
vps-control-room-frontend.service, port 4000. - Production agent service:
vps-control-room-agent.service, loopback port 4001. - Frontend production entrypoint:
node build/index.jsinside the selected immutable release. - Public domain is supplied by
CONTROL_ROOM_DOMAIN/Traefik;ORIGINshould match the public HTTPS origin.
Fast checks
curl -fsS http://127.0.0.1:4000/api/health
curl -I http://127.0.0.1:4000/login
curl -fsS http://127.0.0.1:4001/health
systemctl status vps-control-room-frontend --no-pager
systemctl status vps-control-room-agent --no-pager
journalctl -u vps-control-room-frontend -n 50 --no-pager
For asset issues, inspect the current /_app/immutable/ URLs and verify the active service process cwd points to a valid frontend/releases/svelte-* release containing build/index.js.
Workflow
- Inspect actual git/worktree/service state; never trust an old deployment note blindly.
- Read the owning file (
scripts/deploy.sh,scripts/install-systemd.sh, Traefik config, frontend route, or agent endpoint). - Make the smallest SSOT change; do not add compatibility frontend paths.
- Run frontend check/tests/build and
git diff --checkbefore a frontend switch. - For UI changes, run real login/xterm/SSE and responsive smoke tests.
- After a frontend-only deploy, verify the agent PID did not change.
- Keep rollback material until the new release is verified.
Do not push, merge, rebase, or alter GitHub credentials unless the user explicitly asks.
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.
- yesterday Changed · -26 lines scan B → A b07c4a6bad00
- 6d ago First seen · 65 lines · 0 tokens per session scan B 61de56d7fb3e
vps-control-room is a command published in the GitHub repository rahmanef63/control-room (18 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 511 tokens. A static security scan graded it A with 1 finding (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-deploy
Deploy a PortalJS portal to PortalJS Arc — Datopian-managed static hosting on Cloudflare. Builds a static export, uploads it, and returns a live .arc.portaljs.com URL. One command, one target.
review-system-design
Review a system design someone else provided - screenshot, drawio, Mermaid, slides, doc, or IaC - by extracting it into a confirmed fact sheet, then scoring it on the nine axes.
ship
Commit all staged and unstaged changes, push, create a PR, merge, deploy, and warm caches.
ui-interactive
Interactive component wizard with step-by-step guidance and enforced quality gates.
build
Smart build with validation, error detection, and auto-fix.
feature
Command "feature" from databayt/hogwarts, covering feature development command, usage, basic usage, with detailed requirements and with specific technical constraints.