OpenRoom is a browser-based desktop environment where an AI agent controls built-in applications through natural-language requests and structured actions. People use it to interact with tools such as music, email, diary, games, and other apps through a desktop-like interface running locally in the browser. Its catalogue add-ons provide commands and instructions for working with this environment.
Borrowing it
Nothing to install: this file belongs to MiniMax-AI/OpenRoom. 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/MiniMax-AI/OpenRoom/main/.claude/commands/vibe.mdgit clone --depth 1 https://github.com/MiniMax-AI/OpenRoomWrote 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/minimax-ai/openroom/vibe)<a href="https://agentmods.dev/commands/minimax-ai/openroom/vibe"><img src="https://agentmods.dev/badge/commands/minimax-ai/openroom/vibe.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.01527 |
| Opus 5 | $0.00000 | $0.00763 |
| Sonnet 5 | $0.00000 | $0.00305 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade A, and why
vibe 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 8d 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.
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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeApp Workflow Orchestrator
Single-entry workflow orchestrator. Automatically advances stages based on workflow state, supporting creation, resume from breakpoint, and requirement changes.
Parameter Parsing
$ARGUMENTSformat:{AppName} [Description]- Has Description + App does not exist -> New workflow (creation mode)
- Has Description + App already exists (workflow completed) -> Change workflow (change mode)
- AppName only -> Resume existing workflow (continue from last interruption point)
- AppName --from=XX -> Re-run from specified stage (e.g.,
--from=04-codegen)
Mode Determination Logic
Read .claude/thinking/{AppName}/workflow.json
├── File does not exist ──────────────────────> Creation mode
├── File exists + No Description ─────────────> Resume mode
└── File exists + Has Description
├── Workflow all completed ─────────────> Change mode
└── Workflow not completed ─────────────> Resume mode (ignore new Description, prompt user to complete current workflow first)
Creation Mode: Stage Definitions
01-analysis -> Requirement Analysis
02-architecture -> Architecture Design
03-planning -> Task Planning
04-codegen -> Code Generation
05-assets -> Asset Generation (auto-detected, skipped if no requirements)
06-integration -> Project Integration
Change Mode: Stage Definitions
01-change-analysis -> Change Impact Analysis
02-change-planning -> Change Task Planning
03-change-codegen -> Change Code Implementation
04-change-verification -> Change Verification
Execution Protocol
1. Initialize Workflow State
Read .claude/thinking/{AppName}/workflow.json:
- File does not exist (creation mode):
- Create directory
.claude/thinking/{AppName}/outputs/ - Create
workflow.jsonwith mode set tocreate, all stages set topending,currentStageset to01-analysis - Record user Description in the
descriptionfield ofworkflow.json
- Create directory
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.
- 8d ago First seen · 166 lines · 0 tokens per session scan A 2104a3b32cb0
vibe is a command published in the GitHub repository MiniMax-AI/OpenRoom (1,257 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,527 tokens. 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 commands, from other repositories
BOOTSTRAP
First-run ritual for new agents.
changelog
Create UPCOMINGCHANGELOG.md from the structured changelog input below. If UPCOMINGCHANGELOG.md already exists, ignore its current contents completely. Do not preserve, merge, or reuse text from the existing file.
learn
Extract non-obvious learnings from session to AGENTS.md files to build codebase understanding.
translate
translate English to other languages.
spellcheck
Look at all the unstaged changes to markdown (.md, .mdx) files, pull out the lines that have changed, and check for spelling and grammar errors.
checklist
Generate a custom checklist for the current feature based on user requirements.