devops-wasp-drone — Claude Code subagent: setup and guide
devops-wasp-drone is a Claude Code subagent for container builds and CI/CD workflows in Node.js, Next.js, and TypeScript projects.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install platform-and-release-tools@wasp-nestWhat devops-wasp-drone does
The assistant reviews Dockerfile recipes, dev compose files, and GitHub Actions setups. It enforces multi-stage targets, runs non-root containers, and keeps secrets out of image layers via BuildKit mounts. In continuous integration, it replaces static credentials with OIDC tokens and pins external actions to full commit hashes.
It aligns developer machines with remote runners using Docker Bake or target scripts. Provisioning Kubernetes clusters and authoring database schema changes are strictly outside its scope. Workflows running with excessive permissions or containers executing as root are flagged as immediate blockers.
What it helps with
- convert a single-stage Dockerfile into a lean multi-stage build
- pin third-party GitHub Actions to immutable commit SHAs
- swap permanent cloud access keys for short-lived OIDC federation
- configure container healthchecks to sequence compose dependencies
Example prompts for the agent
- Audit our GitHub Actions workflows for over-privileged tokens and unpinned actions
- Refactor this Next.js Dockerfile using BuildKit cache mounts and a non-root user
- Configure Docker Compose for local dev with healthchecks on the database service
How to install devops-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install platform-and-release-tools@wasp-nest2Manually: put the files in place
.claude/agents/devops-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/devops-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/devops-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about devops-wasp-drone
How to install devops-wasp-drone in Claude Code?
Add the repository with /plugin marketplace add legioncodeinc/vibe-coding-tools, then execute /plugin install platform-and-release-tools@wasp-nest. Alternatively, place the agent definition directly at .claude/agents/devops-wasp-drone.md.
What primary stacks does this agent target?
It targets Node.js, Next.js, and TypeScript ecosystems. General container guidelines apply to other languages, but framework-specific optimisations will be limited.
Does this subagent write database migrations or Kubernetes manifests?
Neither is supported. It links migration execution steps inside deployment pipelines, but schema writing and Helm charts belong to separate tooling.