Vibe Coding Tools

The Wasp Nest

Get the Git life.

184 specialist Drones, 223 Stingers, commands, hooks, and rules across 21 installable plugins.

Give your coding assistant the people, playbooks, and project memory it needs to build.

Want to know what will actually drive more revenue? OSPRY is the insight engine built for exactly that.

Start here

Install Claude Code or Codex, then add the public marketplace. In Claude Code, enter these in the assistant's command prompt:

In a terminal with Codex installed, add the same marketplace and select the core in the plugin browser:

The v3 layout has a required Core and the optional plugins declared in its current catalog. Purge the previous Wasp Nest installation before installing it. Keep Core enabled and select each workflow's prerequisites.

Choose the packs your work needs. Claude skills use their plugin namespace, such as /wasp-nest-core:get-started-stinger; Codex shows skills and command wrappers. Native Codex Drone roles require Core's trusted hook and an explicit registry of enabled package roots. The local installer writes that registry; a marketplace install alone is not proven to do so. Review the selection before trusting /hooks and starting a new session. See harness capabilities.

Open the repository you want to work on and ask:

The first-session hook checks home and project setup locks on supported local hosts. Missing setup prompts an offer. Existing code gets a Knowledge pass before Library setup completes. Read Getting Started before accepting either offer.

The problem this fixes

Your assistant can write code. It still needs your product facts, past decisions and definition of done.

Drones own bounded specialties. Stingers carry methods, examples and cited research. The Library keeps knowledge, plans, issue fixes and…