Skill Claude CodeCodex
Skill "boost-modules" from av/harbor, covering harbor boost custom modules, module structure, quick reference, output methods and stream text to client.
Stop configuring your AI stack. Start using it. One command brings a complete pre-wired LLM stack with hundreds of services to explore.
av/harbor is a command-line tool and companion app that uses Docker Compose to start a connected local stack of language-model backends, user interfaces, and supporting AI services. People use it to run services such as Ollama, llama.cpp, vLLM, Open WebUI, search, voice, and image-generation tools without configuring their connections manually, while the catalogue provides agent workflows for operating Harbor.
This repository also configures its own agents. See what harbor tells them →
Skill Claude CodeCodex
Skill "boost-modules" from av/harbor, covering harbor boost custom modules, module structure, quick reference, output methods and stream text to client.
Skill Claude Code
Use Harbor's Daytona sandbox platform for computer use — creating sandboxes, taking screenshots, sending mouse/keyboard input, and building agent loops. Use when the user wants to interact with a GUI, automate a desktop, do computer use, control a browser visually, or run Claude computer use against a Daytona sandbox.
Skill Claude Code
CLI toolkit for managing containerized LLM services. Use when the user wants to start, stop, configure, or manage AI/LLM services like Ollama, Open WebUI, llama.cpp, vLLM, LiteLLM, ComfyUI, and 250+ others. Triggers on requests to "run a model", "start ollama", "set up an LLM", "configure harbor", "manage services"…
Skill Claude CodeCodex
Comprehensive guide for setting up and running local LLMs using Harbor. Use when user wants to run LLMs locally, set up or troubleshoot Ollama, Open WebUI, llama.cpp, vLLM, SearXNG, Open Terminal, or similar local AI services. Covers full setup from Docker prerequisites through running models, per-service…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: