integrate-module

# Integrate Module Turn any external program into a Genesis module. This is the standardized process for plugging a program into Genesis — whether it was built for Genesis or not. Genesis is the nervous system. The program is the body. This skill builds the connection between them. ## When to Use - User says "integrate X into Genesis" or "make X a module" - User wants to plug an external program, service, or tool into Genesis - User wants Genesis to drive, monitor, or interact with an external system - Ego session discovers a program worth integrating and proposes it ## Input One of: - **Running service URL** (e.g., `http://your-host:8080`) - **Repository URL** (e.g., `github.com/user/repo`) - **Local path** (e.g., `~/my-tool/`) - **Description** (e.g., "a job automation tool running on my server") ## Phase 1: Discovery **Goal:** Understand what the program does, how it communicates, and what Genesis can connect to. ### If running service: 1. Probe for health endpoints: `/health`, `/api/health`, `/status`, `/` 2. Probe for API documentation: `/docs`, `/openapi.json`, `/swagger.json` 3. If OpenAPI spec found: parse all endpoints, methods, parameters 4. If no spec: probe common REST patterns, check response shapes 5. Record: base URL, available endpoints, response formats, auth requirements ### If repository: 1. Clone or read the source 2. Identify tech stack (language, framework, database, scheduler) 3. Find entry points: route definitions, CLI commands, main functio...