MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
Build, migrate, test, link, debug, or package full-trust VibeX v4 product plugins with README summaries, contents, root config, dependencies, App surfaces, editable file tabs, Agent Skills…
Install Vibex Plugin Development
$ npx skills add Xircth/VibeX --skill vibex-plugin-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Xircth/VibeX vibex-plugin-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Xircth/VibeX.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vibex-plugin-development .claude/skills/vibex-plugin-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vibex-plugin-development" agent skill from https://github.com/Xircth/VibeX/tree/master/.agents/skills/vibex-plugin-development into .claude/skills/vibex-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibex-plugin-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Xircth/VibeX/tree/master/.agents/skills/vibex-plugin-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Xircth/VibeX --skill vibex-plugin-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Xircth/VibeX vibex-plugin-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Xircth/VibeX.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/vibex-plugin-development .agents/skills/vibex-plugin-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibex-plugin-development" agent skill from https://github.com/Xircth/VibeX/tree/master/.agents/skills/vibex-plugin-development into .agents/skills/vibex-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibex-plugin-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Xircth/VibeX --skill vibex-plugin-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Xircth/VibeX vibex-plugin-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Xircth/VibeX.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/vibex-plugin-development .cursor/skills/vibex-plugin-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibex-plugin-development" agent skill from https://github.com/Xircth/VibeX/tree/master/.agents/skills/vibex-plugin-development into .cursor/skills/vibex-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibex-plugin-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Xircth/VibeX.git --path .agents/skills/vibex-plugin-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Xircth/VibeX --skill vibex-plugin-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Xircth/VibeX vibex-plugin-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Xircth/VibeX.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/vibex-plugin-development .gemini/skills/vibex-plugin-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibex-plugin-development" agent skill from https://github.com/Xircth/VibeX/tree/master/.agents/skills/vibex-plugin-development into .gemini/skills/vibex-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibex-plugin-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Xircth/VibeX vibex-plugin-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Xircth/VibeX --skill vibex-plugin-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Xircth/VibeX.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/vibex-plugin-development .github/skills/vibex-plugin-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibex-plugin-development" agent skill from https://github.com/Xircth/VibeX/tree/master/.agents/skills/vibex-plugin-development into .github/skills/vibex-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibex-plugin-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Xircth/VibeX --skill vibex-plugin-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Xircth/VibeX vibex-plugin-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Xircth/VibeX.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/vibex-plugin-development .opencode/skills/vibex-plugin-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibex-plugin-development" agent skill from https://github.com/Xircth/VibeX/tree/master/.agents/skills/vibex-plugin-development into .opencode/skills/vibex-plugin-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibex-plugin-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vibex-plugin-development- GitHub stars
- 136
- Token cost
- ~1.7k tokens
- SKILL.md length
- 766 words
- Files
- 5 (incl. scripts, references)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Build, migrate, test, link, debug, or package full-trust VibeX v4 product plugins with README summaries, contents, root config, dependencies, App surfaces, editable file tabs, Agent Skills…
- Works in 5 steps: Run python3… → Read every path printed under required;… → Use the checked-out SDK and CLI… → …
- .vibex-plugin/plugin.json
- SKILL.md covers Load the local contract, Compose the product, Develop against Full Trust and Platform disciplines (ADR-0069), plus 2 more sections
- Runs Python scripts from its folder; calls python3 and pnpm; reaches github.com
What it does
Vibex Plugin Development is an agent skill from Xircth/VibeX. Build, migrate, test, link, debug, or package full-trust VibeX v4 product plugins with README summaries, contents, root config, dependencies, App surfaces, editable file tabs, Agent Skills, workflows, MCP, Workers, and Runtimes. Use for .vibex-plugin/plugin.json, @vibex/plugin-sdk, vibex-plugin CLI, or linked plugin development.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/full-trust.md` and `references/workflow.md`).
It sits in Agent Workflows, covering Hooks and plugins. It works with Model Context Protocol. The repository describes itself as: IADE：A New Development Platform for the AI Era—An Integrated Agent Development Environment. The licence is Apache-2.0.
When your agent uses it
- .vibex-plugin/plugin.json
- @vibex/plugin-sdk
- Vibex-plugin CLI
- Linked plugin development
Example prompts
- “/vibex-plugin-development”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Run python3 .agents/skills/vibex-plugin-development/scripts/locate_toolchain.py from the VibeX repository root.
- Read every path printed under required; stop when one is missing.
- Use the checked-out SDK and CLI versions. Treat online examples as research, not as the active contract.
- Read references/workflow.md for package composition and verification.
- Read references/full-trust.md when authoring executable Worker, App, Runtime, filesystem, network, or external-editor behavior.
What it can do on your machine
Read from SKILL.md and the folder at commit 4a2c06d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vibex Plugin Development loads about 1.7k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 766 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from Xircth/VibeX at commit 4a2c06d, republished under its Apache-2.0 licence (© Xircth). 766 words, ~1,661 tokens.
Download SKILL.mdSave it as
.claude/skills/vibex-plugin-development/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- vibex-plugin-development
- description
- Build, migrate, test, link, debug, or package full-trust VibeX v4 product plugins with README summaries, contents, root config, dependencies, App surfaces, editable file tabs, Agent Skills, workflows, MCP, Workers, and Runtimes. Use for .vibex-plugin/plugin.json, @vibex/plugin-sdk, vibex-plugin CLI, or linked plugin development.
VibeX Plugin Development
Build one user-facing product with one identity, README, root config, content tree, and lifecycle. App, Agent, Host, and Runtime are integration targets inside that product.
The Host product plugin (Skill /create-skill and contract references) lives in the git submodule assets/plugins/plugin-development (https://github.com/Xircth/vibex-plugin-development). Edit that repository for the user-facing Skill. This Skill is the in-tree authoring procedure against the checked-out SDK and CLI.
Load the local contract
- Run
python3 .agents/skills/vibex-plugin-development/scripts/locate_toolchain.pyfrom the VibeX repository root. - Read every path printed under
required; stop when one is missing. - Use the checked-out SDK and CLI versions. Treat online examples as research, not as the active contract.
- Read references/workflow.md for package composition and verification.
- Read references/full-trust.md when authoring executable Worker, App, Runtime, filesystem, network, or external-editor behavior.
Completion criterion: every integration used by the package exists in the local manifest type, validator, Host, and test harness.
Compose the product
- Put the one-line
summaryin README frontmatter and the complete user guide in the README body. - Put Agent/user-readable resources under
contents/and index them in.vibex-plugin/content.index.json. - Put mutable user settings in root
config.json; describe them withconfig.schema. - Put Runtime descriptors under
depends/, source entrypoints underruntime/, and generated output underdist/. - Declare every integration statically. A Skill is optional; at least one real integration is required.
- Use
file.opener + artifact.previewfor Runtime-backed read-only previews. - Use
file.opener.editorSurface + app.surface(slot: artifact.editor)for an editable UTF-8 file tab. Read and save throughbridge.artifact; the App never needs a Host path.
Use only @vibex/plugin-sdk, /worker, /app, /testing, /protocol, and /stdio. If the public SDK cannot express the product, add a generic Host capability, expose it through the SDK, test it, and then consume it from the plugin.
Develop against Full Trust
VibeX v4 executes installed plugin code with the user's trust. There is no permission grant step. Keep package identity, deterministic digest, candidate rollback, revision conflict handling, and lifecycle cleanup intact because they protect correctness and user data. Follow references/full-trust.md.
Platform disciplines (ADR-0069)
- No privileged official plugins. Official plugins use the same public SDK, contribution points, and toolchain as any third party. Never special-case a plugin ID in Host code, and never reach for a private
host.call, slot, or lifecycle. CI enforces this (pnpm run plugin:no-privilege): official packages import only the public SDK, and Host code carries no official-plugin-ID branches. - Single-layer extension. A plugin targets Host contribution points only. Reuse another plugin by copying its source and republishing under a new Publisher + Plugin ID. The derived package installs, stores data, and updates independently. Same-slot coexistence is resolved by the Host.
- A contribution point ships with its first official consumer. New contribution kinds enter the stable surface only together with an official plugin consuming them plus the four acceptance items (CLI validate, Host inspect, real UI/Agent consumption, author docs). Build only against contribution points documented as stable; if a needed extension point is missing, stop at that boundary and deepen the public SDK first.
Show full SKILL.md (278 more words)Show less
Verify the real journey
Run from the plugin root:
vibex plugin run server --http://127.0.0.1:17891 --token <token>
vibex-plugin init . --template host-chrome # or provider-import / full / …
vibex plugin run build
vibex-plugin validate
vibex plugin run test
vibex plugin add --dev .
vibex plugin run dev
vibex plugin run test --host
vibex plugin pack
vibex plugin publishhost-chrome writes one contribution per chrome slot (app.command /
app.toolbar / app.status / app.composer.slash / app.timeline.card /
app.settings.section). panel / kanban-view write one structure surface
each with a Vite Module Federation remote. provider-import writes one
provider.model.importSource. Chrome slots refresh through the activation
generation. Structure remotes use vibex plugin run dev HMR (host loadRemote
points at Vite; leaving dev falls back to dist/remoteEntry.js).
vibex-plugin test --host against a chrome or structure package: install →
enable → declared kinds appear in plugin_contribution_catalog → disable →
they vanish → enable again → uninstall, source directory kept. A Skill-bearing
package still also reloads SKILL.md.
Prefer vibex plugin run server then vibex plugin run dev from the plugin
directory. add --dev only links. vibex-plugin install --link is an alias
of that Host import when it still exists.
The product CLI also exposes vibex plugin pack and vibex plugin publish.
When developing VibeX itself, build the local CLI and use npx-cli
(vibex plugin …). Verify a real linked install and run dev against the
running Host; harness-only success is insufficient for App mounting, file
editing, Runtime processes, or remote behavior.
Completion gate
- The plugin imports only public SDK modules and contains no VibeX-source special case.
- Manifest, SDK, CLI validation, Host parsing, and UI consumption agree on every contribution.
- Worker and App harnesses cover registration, load, save, conflict/error, dispose, and candidate rollback paths that apply.
- Build, validate, test, doctor, and deterministic pack pass.
- A real linked package activates, its user-visible function works end to end, and uninstall/data-retention behavior is documented.
- README explains requirements, operation, offline/network behavior, troubleshooting, and third-party licenses.
When a required extension point is absent, stop plugin implementation at that boundary and deepen the public SDK first.
© Xircth, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references) in .agents/skills/vibex-plugin-development of Xircth/VibeX.
- SKILL.md
- agents/openai.yaml
- references/full-trust.md
- references/workflow.md
- scripts/locate_toolchain.py
Open the folder on GitHubat commit 4a2c06d
Compare with similar skills
Vibex Plugin Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibex Plugin Development this skillXircth/VibeX | 136 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| OpenpetsOpenPetsHQ/openpets | 1.3k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Claude Automation Recommenderanthropics/claude-plugins-official | 38k | 3 repos | ~2.7k | Automated safety check: Notes | Apache-2.0 | |
| Mistral Vibe Plugin Creatormistralai/mistral-vibe | 5.1k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Openpets
OpenPetsHQ/openpets
A skill your agent uses whenever the user wants to build, extend, debug, test, validate, locally load, package, or publish an OpenPets plugin; work with the OpenPets Plugin SDK v3, plugin manifest…
- Official
Claude Automation Recommender
anthropics/claude-plugins-official
Scans a codebase and suggests which Claude Code hooks, subagents, skills, plugins and MCP servers fit its stack, without changing any files.
- Official
Mistral Vibe Plugin Creator
mistralai/mistral-vibe
Shows how to build a Vibe plugin package in the Agent Plugins 1.0 format, with a plugin.json manifest and optional skills, MCP servers, hooks and other components.
Agent Setup Health Audit
tw93/Waza
Audits a project's agent configuration, instruction drift, hooks, MCP and AI maintainability, then reports prioritized findings with evidence and next actions.
More from Xircth/VibeX
Understand Dashboard
Xircth/VibeX
Launch the interactive web dashboard to visualize a codebase's knowledge graph
Understand
Xircth/VibeX
Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
Maiden Skill
Xircth/VibeX
Project-wide engineering principles for VibeX. An agent skill from Xircth/VibeX.
Vibex Workflow Creator
Xircth/VibeX
Design, edit, validate, publish, inspect, and debug VibeX .vibex-workflow.json DAGs with the dedicated vibex-workflow-mcp.
Implement Spec
Xircth/VibeX
Implement a specification in code.
Related
Works with
Categories
Questions about Vibex Plugin Development
What does Vibex Plugin Development do?
Build, migrate, test, link, debug, or package full-trust VibeX v4 product plugins with README summaries, contents, root config, dependencies, App surfaces, editable file tabs, Agent Skills…. Vibex Plugin Development is an agent skill from Xircth/VibeX. Build, migrate, test, link, debug, or package full-trust VibeX v4 product plugins with README summaries, contents, root config, dependencies, App surfaces, editable file tabs, Agent Skills, workflows, MCP, Workers, and Runtimes.
When should I use Vibex Plugin Development?
Vibex Plugin Development fits situations like: .vibex-plugin/plugin.json; @vibex/plugin-sdk; vibex-plugin CLI; linked plugin development.
How do I install Vibex Plugin Development in Claude Code?
Run `npx skills add Xircth/VibeX --skill vibex-plugin-development -a claude-code`. Or copy the skill folder (.agents/skills/vibex-plugin-development in Xircth/VibeX) into .claude/skills/vibex-plugin-development in your project. Claude Code loads it when a task matches its description.
How do I install Vibex Plugin Development in Codex?
Run `npx skills add Xircth/VibeX --skill vibex-plugin-development -a codex`. Or copy the skill folder (.agents/skills/vibex-plugin-development in Xircth/VibeX) into .agents/skills/vibex-plugin-development in your project. Codex loads it when a task matches its description.
Can I use Vibex Plugin Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Xircth/VibeX --skill vibex-plugin-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibex-plugin-development, .gemini/skills/vibex-plugin-development, .github/skills/vibex-plugin-development and .opencode/skills/vibex-plugin-development in your project.
What does Vibex Plugin Development need to run?
Going by SKILL.md and its folder, Vibex Plugin Development needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and pnpm). Our summary lists: Python 3.
Does Vibex Plugin Development access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Vibex Plugin Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Vibex Plugin Development use?
Vibex Plugin Development is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibex Plugin Development use?
About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.
What are the alternatives to Vibex Plugin Development?
Skills that share tags, products or a category with Vibex Plugin Development: MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars), Crush Configuration (charmbracelet/crush, 29k stars), Openpets (OpenPetsHQ/openpets, 1.3k stars) and Claude Automation Recommender (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibex Plugin Development?
Xircth (a GitHub user) maintains it in Xircth/VibeX, which has 136 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 29, 2026.
Source: Xircth/VibeX on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.