HYPERVIBE
Plugin · OpenCode

Hypervibe for OpenCode

You use OpenCode, the open source coding assistant that works with the model of your choice? The Hypervibe plugin runs there too: the same skills, the same guardrails, and the same way of building an application by describing it.

What you get

Exactly the same plugin as for Claude Code, converted on the fly from the current version: the 88 skills (including /start, /bootstrap and every add-*), the scripts they drive, the context7 MCP server, and the guardrail that refuses irreversible commands. In OpenCode, every skill becomes a command: /start, /bootstrap, /add-db.

A small OpenCode plugin, generated with the archive, runs the guardrail before every command and turns its confirmation requests (publishing, deploying to production, writing to the database) into OpenCode's native permission prompts. It also brings the MCP server and its rules: you have no configuration file to edit.

Download the OpenCode version

Version 3.1.7, converted for OpenCode from the current version of the plugin

Download for OpenCode

A .zip archive. Do not unzip it yourself: the next step takes care of it. On a Mac, if Safari already unfolded it into a folder, compress that folder again before going on.

Install, without writing a line of code

OpenCode is an assistant: it does the installing. You download, you paste it one sentence, and you open a new session.

  1. Download the archive above. It lands in your Downloads folder.
  2. Open OpenCode (with a model provider connected) and paste it this sentence:
    No need to read it: it is addressed to OpenCode.

    OpenCode first asks for permission to access your Downloads folder, then its configuration folder: accept both. It unzips the archive in the right place and checks its contents. Nothing else to configure: the generated plugin brings the guardrail, the MCP server and the permission rules when OpenCode starts.

  3. Close OpenCode and open a new session. Type /start to check your setup and connect your accounts, exactly as in Claude Code. Every skill answers to /name.

OpenCode works with the model provider you connect to it (OpenAI, Anthropic, or another). The skills are written for a current-generation model: the more capable it is, the smoother they run.

Prefer to do it by hand?
  1. Open the .config/opencode folder of your user folder (it is hidden: paste its path in the address bar of your file explorer).
  2. Unzip the archive and put its contents directly inside: you must end up with skills/hypervibe and plugins/hypervibe-guard.js in that folder.
  3. Open a new OpenCode session.

What differs from Claude Code

  • The rules file is named AGENTS.md, the one OpenCode reads first, instead of CLAUDE.md. If you also use Claude Code on the same machine, OpenCode reads your CLAUDE.md as long as no AGENTS.md sits next to it.
  • When a skill has a question for you, it goes through OpenCode's question tool, where Claude Code shows a menu of choices.
  • Confirmations before an irreversible action (publishing, deploying to production, writing to the database) are OpenCode's native permission prompts, with its keyboard shortcuts.
  • A few skills still describe menus that only Claude Code has. Everything else, key vault included, is the same scripts.

Updating: with each new plugin version, download the archive again and repeat. The install is rebuilt from scratch and keeps nothing of its own.

Frequently asked questions

No. The OpenCode version stands on its own: you need OpenCode, a connected model provider, and Node.js, which /start installs when missing. Claude Code plays no part.

The one you connect to OpenCode. The skills are tested with recent OpenAI and Anthropic models; a weaker model follows the steps with more hesitation.

Yes. The generated plugin runs exactly the same rules as under Claude Code before every command: a sweeping git add or a table drop is refused with the explanation. What needs your agreement goes through OpenCode's permissions, which ask you on screen.

No. The generated plugin brings the MCP server and the permission rules when OpenCode starts, without touching your configuration file. Removing it means deleting two folders.

Going further