install

An AI engineering team for your coding agent.

Give your coding agent a team that plans the work, builds it in parallel, tests, reviews, and ships. One command installs it — keep working in Claude Code, Codex, or OpenCode.

Get started

22 agents 18 skills 13 commands 6 workflows

agentkrew · init → /create-feature

npx @agentkrew/cli init

? Runtime (claude, codex, opencode) [claude]: claude

AgentKrew engineer kit installed (runtime: claude).

now just ask — in plain English

Add password reset emails — with tests.

tech-lead plans the work

backend-architect builds the API

frontend-specialist builds the UI

database-specialist shapes the schema

test-automator writes the tests

security-auditor audits the diff

code-reviewer reviews the changes

shipper ships it

shipped · 6 steps · in your coding agent

example · init output abridged · stage order from the shipped feature-development workflow · + stages run together

how it works

Three steps and you're running

No servers, no config files to learn. One command installs the team, and your coding agent picks it up from there.

  1. 01

    npx @agentkrew/cli init

    Pick your coding agent and a kit, glance at the file preview, done. Nothing you wrote gets overwritten.

  2. 02

    open your coding agent

    Your new team is picked up automatically — no server, no extra setup, nothing else to install.

  3. 03

    /create-feature "Add Stripe checkout"

    Type a command or just describe what you want — the team plans the work, builds it in parallel, tests, reviews, and ships.

kits

Two teams, one format

Two ready-made teams — agents, skills, slash commands, and workflows. Install one, or run both together.

Engineer Kit

Engineering agents, skills, commands, and workflows — the team that plans, builds, tests, audits, reviews, and ships software.

15 agents 18 skills 7 commands 3 workflows

workflows: bug-fix · feature-development · review

Marketing Kit

Marketing agents, skills, commands, and workflows — the team that takes what you ship to market: research, brand, content, SEO, and launch plans.

7 agents 6 commands

Cross-kit workflows

Cross-kit workflows requiring both engineer and marketing. Requires both kits, so one feature ships with engineering and marketing already in sync.

feature-launch · marketing-campaign · product-launch

runtimes

Runtime support

Install once and keep the coding agent you already use. Claude Code, Codex, and OpenCode all work — and AgentKrew never edits your CLAUDE.md, AGENTS.md, or opencode.json.

Claude Code

default

.claude/agents/<name>.md

One subagent per kit agent, plus .claude/commands/ and .claude/skills/. Invoked automatically via the Task tool, or explicitly with @tech-lead.

Read the guide →

Codex

supported

.codex/agents/<name>.toml

Custom agents in TOML, skills under .agents/. Spawned by description match or via a cmd- plan.

Read the guide →

OpenCode

supported

.opencode/agents/<name>.md

Subagents with mode: subagent frontmatter, plus commands and skills under .opencode/. Automatic or @mention.

Read the guide →

agents

Agents

One specialist per job, each with a description your coding agent uses to pick the right one — or name it yourself with @tech-lead.

engineer · 15 agents

  • accessibility-specialist Audits and fixes WCAG keyboard, ARIA, contrast, and screen-reader issues
  • api-designer Designs versioned REST API contracts with pagination, errors, and compatibility
  • backend-architect Designs backend architecture and APIs
  • code-reviewer Reviews correctness, maintainability, and test coverage

marketing · 7 agents

  • brand-voice Keeps messaging consistent with the project's voice and tone guidelines
  • competitive-analyst Compares competitors and surfaces positioning gaps to exploit
  • content-marketer Plans and drafts blog posts and editorial content that earns attention
  • copywriter Writes concise emails and landing pages that drive one action

all 22 agents in the docs →

skills

Skills

Reusable know-how your agent loads only when it's needed — patterns, pitfalls, and checklists — instead of cramming everything into every prompt.

18 skills shipped today — see them all →

accessibility

WCAG keyboard, ARIA semantics, contrast, and screen-reader verification

api-design

Versioned REST contracts with pagination, filtering, and uniform errors

docker

Minimal pinned container images, compose environments, and CI delivery

error-analysis

Reading stack traces, logs, and error shapes to pinpoint failure origins

git

Focused commits, safe branching, reviewable diffs, and history hygiene

nextjs

Next.js App Router pages, server/client boundaries, and data fetching

commands

Commands

The shortcuts you type. Each one runs a workflow or asks an agent — like /create-feature, /review, or /ship.

  • /create-feature workflow: feature-development Implement a new feature via the feature-development workflow
  • /fix-bug workflow: bug-fix Fix a bug via the bug-fix workflow
  • /multi-agent-review workflow: review Review a scope with parallel reviewers and one aggregated verdict
  • /review workflow: review Review implementation via the review workflow

all 13 commands in the docs →

compare

Compared to a general-purpose agent

The baseline: one general-purpose coding agent with hand-written rules files. It works — until the work needs a team.

  General-purpose agent + rules files AgentKrew
Team One agent playing every role A named specialist for every job
Knowledge Rules you edit by hand and re-explain Skills your agent loads when it needs them — patterns, pitfalls, checklists
Execution One chat, everything in a row A plan first, then specialists work in parallel
Runtimes Re-do the setup in every tool Install once — Claude Code, Codex, and OpenCode
Changes Copy-paste and hope nothing conflicts agentkrew update refreshes generated files; yours are never touched
Entry points Whatever you remember to type Slash commands: type /create-feature and go

nothing to uninstall — your own files are never touched

pricing

Pricing

One payment, yours to keep: all future updates for the kit(s) you buy. Every kit update ships to you at no extra cost.

  • pay once — all yours, no subscription
  • lifetime updates: all future updates for the kit(s) you buy
  • 14-day refund, no questions asked

Engineer Kit

$49 one-time

  • 15 agents
  • 18 skills
  • 7 commands
  • 3 workflows
Comming soon

Both kits

save $9

$89 one-time

  • 15 agents
  • 18 skills
  • 7 commands
  • 3 workflows
  • 7 agents
  • 0 skills
  • 6 commands
  • cross-kit workflows
Comming soon

prices in USD · license delivered as AGENTKREW_LICENSE_KEY · the CLI itself is free

faq

FAQ

The questions that come up before installing.

What exactly do I get?

Two ready-made teams — Engineer and Marketing — each with agents, skills, slash commands, and workflows, plus the free @agentkrew/cli that installs them into your coding agent. The kits section lists today's exact contents.

Which coding agents are supported?

Claude Code, Codex, and OpenCode — install once and keep the coding agent you already use. See runtime support and the runtime guides.

Will it rewrite my CLAUDE.md or AGENTS.md?

No. Your own CLAUDE.md, AGENTS.md, and opencode.json are yours: AgentKrew never writes them. Generated files live under .claude/,.codex/, or .opencode/ — plus .agentkrew.json and a create-only AGENTKREW.md — and agentkrew update refreshes only those.

Does it phone home at runtime?

There is no server or daemon. Workflows turn into step-by-step plans your agent follows, and everything runs from files in your project. License checks and kit downloads happen only in the CLI, against api.agentkrew.dev.

How does pricing work?

A one-time payment: $49 per kit, or $89 for both — with all future updates for the kit(s) you buy. Details in pricing.

What are the requirements?

Node.js 22 or newer and one supported coding agent. Install with npx @agentkrew/cli init — it previews every file before writing anything.

Do I need to write any config or YAML?

No. Run npx @agentkrew/cli init, answer two questions, and work in plain English from there. Everything installs with sensible defaults, and you only touch files later if you want to customize.