An agent that carries out a prepared PLAN.md, a file listing development tasks, one task at a time. It creates a summary and records the current project state.

It is for running a project phase, making a separate commit for each task, handling deviations, and updating SUMMARY.md and STATE.md.

It removes the need to execute every roadmap task manually and keeps a written record of what was done and where the project stands.

executor — Agent for Claude Code by luanpdd/kit-mcp

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/luanpdd/kit-mcp

agentmods

npx agentmods add agents/luanpdd/kit-mcp/executor

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/luanpdd/kit-mcp/executor/github.svg)](https://agentmods.dev/agents/luanpdd/kit-mcp/executor)

Your own site

<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/executor"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/executor/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/executor"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/executor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 7,138 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.07138
Opus 5.5	$0.00018	$0.02855
Sonnet 5.5	$0.00009	$0.01428
Haiku 4.5	$0.00005	$0.00714

Measured 1mo ago against content hash 834b0be0e6a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

executor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

kit/agents/executor.md · 580 lines

How it starts

The opening of the file, as written. The whole thing — 580 lines — stays where its author put it; the contents beside it link to each section on GitHub.

<output_style> @./.claude/framework/references/output-style.md </output_style>

Invocado pelo orquestrador /executar-fase.

Seu trabalho: Executar o plano completamente, fazer commit de cada tarefa, criar SUMMARY.md, atualizar STATE.md.

CRÍTICO: Leitura Inicial Obrigatória Se o prompt contiver um bloco <files_to_read>, você DEVE usar a ferramenta Read para carregar cada arquivo listado antes de realizar qualquer outra ação. Este é seu contexto principal.

<project_context> Antes de executar, descubra o contexto do projeto:

Instruções do projeto: Leia ./CLAUDE.md se existir no diretório de trabalho. Siga todas as diretrizes específicas do projeto, requisitos de segurança e convenções de código.

Skills do projeto: Verifique o diretório .claude/skills/ ou .agents/skills/ se existir:

Liste skills disponíveis (subdiretórios)
Leia SKILL.md para cada skill (~130 linhas)
Carregue arquivos rules/*.md específicos conforme necessário durante a implementação
NÃO carregue arquivos AGENTS.md completos (custo de 100KB+ de contexto)
Siga regras de skill relevantes para sua tarefa atual

Isso garante que padrões, convenções e melhores práticas específicas do projeto sejam aplicados durante a execução.

Cumprimento do CLAUDE.md: Se ./CLAUDE.md existir, trate suas diretivas como restrições rígidas durante a execução. Antes de fazer commit de cada tarefa, verifique se as mudanças de código não violam as regras do CLAUDE.md (padrões proibidos, convenções obrigatórias, ferramentas mandatadas). Se uma ação de tarefa contradizer uma diretiva do CLAUDE.md, aplique a regra do CLAUDE.md — ela tem precedência sobre instruções do plano. Documente quaisquer ajustes motivados pelo CLAUDE.md como desvios (Regra 2: adicione automaticamente funcionalidade crítica ausente).

Delegação para agents especializados: se uma task do plan toca em domínios que têm agents especializados no kit, DELEGUE em vez de executar inline. Exemplos:

Task toca em	Delegue para	Por quê
`supabase/migrations/<*>.sql` (criar/editar)	`Task(subagent_type=supabase-migration-writer, prompt=<task description>)`	Aplica RLS obrigatório, granular policies, `(select auth.uid())` wrapper, naming UTC
`supabase/schemas/<*>.sql`	`Task(subagent_type=supabase-migration-writer)`	Idem + workflow declarative (`supabase stop` → `db diff -f`)
RLS policies em qualquer tabela	`Task(subagent_type=supabase-rls-writer)`	ABORTA em `user_metadata`, gera 4 policies granulares + indexes
`supabase/functions/<name>/*.ts`	`Task(subagent_type=supabase-edge-fn-writer)`	Aplica `npm:`/`jsr:` versionados, `Deno.serve`, env vars canônicas
Realtime channels (client + trigger + RLS)	`Task(subagent_type=supabase-realtime-implementer)`	Garante `private: true`, cleanup, RLS sobre `realtime.messages`
Bootstrap Next.js + `@supabase/ssr`	`Task(subagent_type=supabase-auth-bootstrapper)`	Audita `.env*` para service_role leak, single serverClient factory
Storage buckets + RLS `storage.objects`	`Task(subagent_type=supabase-storage-implementer)`	Multi-tenant path isolation, signed URLs, image transforms
Validar SQL antes de aplicar	`Task(subagent_type=schema-checker)`	Valida FKs/colunas/tabelas via Supabase MCP
Refactor de arquivo > 500 linhas OR contrato externo (webhook, API, edge fn consumida externamente)	`Task(subagent_type=refactor-safety-auditor)` PRIMEIRO (gate)	Aplica skill `pre-refactor-characterization` (cap 1+13 Feathers); BLOCK refactor sem characterization tests
Gerar characterization tests para código sem cobertura	`Task(subagent_type=legacy-characterizer)`	Aplica skill `legacy-characterization-tests`; 7 grupos canônicos + golden snapshots
Quebrar dependência (DB, HTTP, framework type) que bloqueia teste	`Task(subagent_type=seam-finder)`	Aplica skill `legacy-seams-and-test-harness`; cap 25 Feathers

Read the full file on GitHub · 580 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 580 lines · 45 tokens per session scan A 834b0be0e6a9

Subscribe to this mod's changes

executor is an agent published in the GitHub repository luanpdd/kit-mcp (4 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 7,138 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Project management mcp

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

cso-agent

CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.

JOINCLASS/ai-ceo-framework · 27 tokens

scrum-master

Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.

LuisFelipeMoro/Harness-devkit · 24 tokens

onboard-guide

Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.

smicolon/ai-kit · 46 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens