# executor

executor — a subagent takes a well-defined task from an orchestrator, edits code, runs commands, and reports the result. Use it to delegate implementation work.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 7523 repo stars
- Author: Devin-AXIS
- License: LicenseRef-Proprietary · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Devin-AXIS/iPolloWork/tree/HEAD/.opencode/agents/executor.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/executor

## What it does

\`executor` handles focused development tasks: it writes or edits code, runs repository commands, and sends back a record of changed files and outcomes. Before reporting, it runs a type check, lint, test, or build when a quick check is available.

The agent follows the repository’s `AGENTS.md` rules, including `pnpm`, avoiding `any` and `as` casts, keeping the diff small, and preferring `@/components` with `shadcn/ui` and Base UI. An underspecified task is a stop condition, not an invitation to guess. Its configuration uses `openai/gpt-5.5-fast` with the `xhigh` variant.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/executor.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/executor.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/executor.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Devin-AXIS/iPolloWork/tree/HEAD/.opencode/agents/executor.md

## When to use it
- delegate a defined coding task to an orchestrator
- edit project files according to a concrete plan
- run an available build, lint, or test check
- report every touched file and its result
- record assumptions and unfinished follow-ups

## Example prompts
- Ask the orchestrator to send `executor` a concrete task for `src/...`, then verify the build and report changed files.
- Have `executor` fix the issue in `src/...`, run the available tests, and return the results.
- Send `executor` a narrowly defined repository task and stop if its requirements are ambiguous.

## Similar
- [coding](https://affpapa.org/en/nevibecode/skills/coding.md) — skill · 394 installs
- [senior-coding-interview](https://affpapa.org/en/nevibecode/skills/senior-coding-interview.md) — skill · 181 installs
- [implement](https://affpapa.org/en/nevibecode/skills/hyperb1iss-implement.md) — skill · 577 installs
- [daily-coding](https://affpapa.org/en/nevibecode/skills/daily-coding.md) — skill · 376 installs
- [ns-coder](https://affpapa.org/en/nevibecode/skills/ns-coder.md) — skill · 151 installs
- [anti-overengineering](https://affpapa.org/en/nevibecode/rules/anti-overengineering.md) — rule · ★ 41178 repo stars

## Other versions with the same name
- [executor · ai-driven-dev](https://affpapa.org/en/nevibecode/agents/ai-driven-dev-executor.md) — ★ 571 repo stars

From the same set: [devin-axis/ipollowork](https://affpapa.org/en/nevibecode/by/devin-axis/ipollowork.md) — 42 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
