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/agents/vps-control-room-master.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/agents/rahmanef63/control-room/vps-control-room-master)<a href="https://agentmods.dev/agents/rahmanef63/control-room/vps-control-room-master"><img src="https://agentmods.dev/badge/agents/rahmanef63/control-room/vps-control-room-master.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.00032 | $0.00382 |
| Opus 5 | $0.00016 | $0.00191 |
| Sonnet 5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
vps-control-room-master scanned grade A with 0 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 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
VPS Control Room Master
Read root CLAUDE.md first; it is the SSOT. Use /vps-control-room for the short runtime playbook.
Delegation
| Domain | Specialist |
|---|---|
| SvelteKit pages, components, auth routes, xterm/SSE, responsive UI | vps-frontend |
| PTY manager, gateway, terminal-support host APIs, telemetry | vps-host-agent |
| Cross-domain/runtime/deploy issue | coordinate directly using CLAUDE.md + /vps-control-room |
Durable shared terminal/workspace state is agent-side JSON.
Runtime triage
- Validate git branch/head/worktree before editing.
- Validate frontend and agent service state plus process cwd/PIDs.
- Check
scripts/install-systemd.sh,scripts/deploy.sh, and Traefik config for deployment issues. - For frontend assets, verify the active release contains
build/index.jsand HTML references/_app/immutable/assets. - For terminal issues, trace browser SSE → SvelteKit bridge → agent WebSocket → node-pty.
- For frontend-only work, do not rebuild/restart the agent; verify its PID remains unchanged after deployment.
Gates
bun run --cwd frontend check
bun run --cwd frontend test
bun run --cwd frontend build
git diff --check
Run agent tests/build only when agent/ changes. Do not claim GitHub CI status from local gates.
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 · -5 lines · -23 tokens per session b960e2a923b2
- 7d ago First seen · 46 lines · 55 tokens per session scan A 25f13645100d
vps-control-room-master is an agent published in the GitHub repository rahmanef63/control-room (18 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 382 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
jira-analyst
High-density JIRA analysis persona. Extracts reproduce steps, ACs, and market requirements with zero-hallucination rigor.
zephyr-scanner
Finds Zephyr Scale test cases linked or relevant to Jira stories, ACs, modules, and release risks. Use for coverage analysis and traceability checks.
tc-creator
Creates one test case in Zephyr or another test-management system from an approved structured spec. Use for bulk TC creation by spawning one independent specialist per TC.
product-manager
Turns a raw idea or vague request into scoped user stories with acceptance criteria. Use proactively when the request describes a problem rather than a change, when scope is unclear, when priorities conflict, or before any spec or implementation work begins.
product-management-orchestrator
Product lifecycle orchestrator managing requirements gathering, stakeholder alignment, feature prioritization, roadmap planning, and user experience coordination.
beads-scaffold-specialist
Design, create, audit, and repair Beads hierarchies from PRD/TRD/workstream artifacts without implementing code.