lazycodex

Install the OpenCode OmO and lazycodex GrokBuild port from the lfg package.

5|Updated May 17, 2026
One-click install
npx skills add https://github.com/islee23520/lfg --skill lazycodex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lazycodex
Source: https://github.com/islee23520/lfg/tree/main/skills/lazycodex
Command: npx skills add https://github.com/islee23520/lfg --skill lazycodex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users install and configure the OpenCode OmO and lazycodex GrokBuild port without manually assembling plugin files, adapter paths, or model settings.

Core Features & Use Cases

  • GrokBuild Plugin Installation: Sets up the lfg package surface as the Grok-native OMO plugin and installs it into the expected Grok plugin directory.
  • Model and Context Setup: Supports interactive model discovery, alias mapping, and context-window aware setup for OpenAI-compatible backends.
  • Repair and Refresh Workflows: Handles sync, refresh, and force-reinstall scenarios for healthy installs, upgrades, and recovery from broken plugin trees.

Quick Start

Ask the assistant to install the lazycodex GrokBuild port with lfg and configure the available models for your Grok Build environment.

Frequently Asked Questions about lazycodex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install the GrokBuild port for OpenCode OmO plugins?

To install the GrokBuild port, the lfg package sets up the Grok-native OMO plugin and deploys it directly into the expected Grok plugin directory without manual file assembly.

What is the best way to sync models for an OpenAI-compatible backend in Grok Build?

Model synchronization uses interactive discovery from the /v1/models endpoint to apply alias mapping and context-window aware setup for OpenAI-compatible backends within Grok Build.

Do I need an OpenAI-compatible base URL to configure GrokBuild plugins?

Yes, configuring GrokBuild plugins requires an OpenAI-compatible base URL to enable native first-party OMO hooks, model discovery, and legacy fallback plugin path support.

Can I repair a broken Grok Build plugin tree without reinstalling everything?

Yes, you can repair broken Grok Build plugin trees using sync, refresh, and force-reinstall workflows that restore healthy installs and recover adapter paths automatically.

Does GrokBuild support legacy fallback plugin paths for OMO installation?

Yes, GrokBuild OMO plugin installation supports legacy fallback plugin paths alongside native first-party OMO hooks to maintain compatibility across different plugin directory structures.