The Wasp Nest plugin

Marketplace of 21 plugins for Claude Code and Codex: 184 specialist agents, 223 skills and a project knowledge library.

  • 95 ★ on the repository
  • Last commit
Plugin

Extended access

Why this level

  • First-session hooks and agents write Library files and instructions, including in the home directory, after your consent.
All reasons and checks

legioncodeinc/vibe-coding-tools

Install

Manual install

/plugin marketplace add legioncodeinc/vibe-coding-tools

Then `/plugin install wasp-nest-core@wasp-nest` and pick the packs you need.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • First-session hooks and agents write Library files and instructions, including in the home directory, after your consent.

This is third-party code. Review the repository files before installing.

What it does

The Wasp Nest packs 184 specialist agents (Drones), 223 skills (Stingers), commands, hooks and rules into 21 installable plugins. The required core `wasp-nest-core` goes in first, and other packs are chosen to fit your workflows. Skills carry methods, examples and cited research, while agents own narrow areas. Shared project memory is called the Library. It holds system knowledge and ADR decision records, PRD requirements, IRD bug write-ups and `CTR-###` contracts that several plans rely on. The `/plan-product`, `/pest-controller` and `/smoke-it` commands lead from a request to verified code. The `library/notes/` folder is for humans only and the agent does not read it.

Who it is for. Teams on Claude Code or Codex that need shared requirements, decision records and contracts between plans.

Good fit when

  • A new product must go from strategy and design to a wave plan and a definition of done.
  • Two plans depend on one API or event and the contract must be agreed by exact revision.
  • A tracked bug is fixed with a root-cause write-up and proof of the result.
  • A new agent needs current system knowledge and the reasons behind architecture choices.

Not a fit when

  • You need a quick one-file edit without documents or approvals.
  • First-session hooks and home instruction changes are not allowed.
  • The team is not ready to keep a Library as a working project folder.

Example request

Use the Get Started Stinger to inspect this repository, explain the home instruction and Library setup, ask before changing anything and show the diff and setup report.

Limitations

Remove the previous Wasp Nest installation before installing a new release. The core is required, and packs are chosen with workflow dependencies in mind. Native Codex Drone roles need the core trusted hook and an explicit registry of enabled package roots: the local installer writes that registry, and a marketplace install alone is not guaranteed to. Review the selection before trusting `/hooks` and opening a new session. The first-session hook offers to set up home instructions and the Library, and the agent asks before changes. The license is in LICENSE.md.

How to disable. Disable the plugins with `/plugin uninstall` for each pack in Claude Code or remove them through the Codex plugin browser. The project `library/` folder stays as plain documents.

FAQ

What are Drones and Stingers?

Drones own narrow specialties and Stingers carry methods, examples and cited research. The repository has 184 agents and 223 skills.

What does the Library hold?

System knowledge and ADRs, PRD requirements, IRD bug write-ups by issue number and `CTR-###` contracts between plans. The `library/notes/` folder stays human-only.

Where do I start after installing?

Open your project and ask the Get Started Stinger to inspect the repository. It explains the setup, asks consent and shows the diff and a report.

How are skills called in Claude Code?

Through the plugin namespace, for example `/wasp-nest-core:get-started-stinger`. Codex shows skills and command wrappers.

What happens with a draft contract?

Dependent work waits until you accept the exact revision of the contract, while unrelated tasks continue.

Discussion

No questions or reviews yet.

Plugins

Softaworks Agent Toolkit

Softaworks Agent Skills

A marketplace of skills, subagents and commands for coding agents: development, documentation, planning and workplace communication

PluginExtended access2.7KRepository stars

Agentic Plugin Marketplace by wshobson

Agentic Plugin Marketplace

94 plugins, 202 agents, 183 skills and 105 commands for Claude Code, generated for Codex, Cursor, OpenCode and Copilot

PluginExtended access42.5KRepository stars

Claude Code kit with eight phase agents, 21 skills and hooks that keep the agent inside set limits.

PluginExtended access79Repository stars

A Codex plugin adds development discipline, 29 skills, 31 hooks and multi-model subagents in one package.

PluginExtended access54Repository stars

A marketplace of 18 Claude Code plugins: access to blocked pages, second-model review, design systems from a site, research and planning

PluginBroad access1.3KRepository stars

A universal workflow plugin for Claude Code: 7 agents, 26 commands, 14 skills and 14 hooks for any project

PluginBroad access1.4KRepository stars

README in short

A public marketplace at v3: a required core and optional plugins from the current catalog. The repository keeps manifests for Claude Code, Codex and Cursor, guides in the learn folder and a harness capabilities reference.

README badge

Report a problem