A structured workflow for handling a project from clarification and planning through execution and delivery. It breaks the process into eight ordered steps, including checking assumptions, mapping repository files, and delegating work when appropriate.

Use it to guide complex repository tasks from an initial request to a validated handoff.

It helps prevent coding from starting before the goal, scope, constraints, dependencies, and risks are understood.

orquestar — Command for Claude Code by Mazalucas

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/Mazalucas/El-DT-Lightweight-Army

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/commands/mazalucas/el-dt-lightweight-army/orquestar/github.svg)](https://agentmods.dev/commands/mazalucas/el-dt-lightweight-army/orquestar)

Your own site

<a href="https://agentmods.dev/commands/mazalucas/el-dt-lightweight-army/orquestar"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/orquestar/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/commands/mazalucas/el-dt-lightweight-army/orquestar"><img src="https://agentmods.dev/badge/commands/mazalucas/el-dt-lightweight-army/orquestar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 818 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.00000	$0.00818
Opus 5.5	$0.00000	$0.00327
Sonnet 5.5	$0.00000	$0.00164
Haiku 4.5	$0.00000	$0.00082

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

Security

Grade A, and why

orquestar 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.

.claude/commands/orquestar.md · 83 lines

How it starts

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

Pipeline Orquestador

Macro (4 fases) vs micro (8 pasos): el core del DT resume el flujo en 4 fases (Clarificar → Planificar y validar → Ejecutar → Entregar). Este comando es el desglose en 8 pasos; no es un pipeline alternativo. Fuente canónica del par macro/micro: regla 00-orquestador-core (no redefinir el modelo en otros lugares; enlazar). Vitals: vitals/INDEX.md.

Ejecuta el pipeline completo del Director Técnico. Sigue estos 8 pasos en orden.

Paso 1: Clarificar

Antes de actuar, clarifica:

Objetivo: ¿Qué se busca lograr?
Restricciones: ¿Hay límites de tiempo, tecnología, alcance?
Alcance: ¿Qué está incluido y qué no?

Si hay ambigüedad, haz preguntas. No asumas.

Paso 2: Cuestionar

No apruebes sin validar. Pregunta:

"¿Consideraste X?"
"¿Qué pasa si Y?"
"¿Hay riesgos o dependencias no mencionadas?"

Solo después de validar, continúa.

Paso 3: Mapear

Identifica los archivos relevantes del repo para la tarea:

Carpetas clave
Dependencias
Puntos de entrada

Paso 4: Delegar (si aplica)

Si la tarea requiere investigación profunda, verificación paralela o documentación, delega a subagentes:

arquitecto: diseño backend, APIs, patrones
frontend: implementación UI, componentes
qa: test plans, edge cases, validación
doc: documentación
researcher: investigación, análisis

Consulta el catálogo de subagentes para decidir cuál invocar. Incluye los protocolos DT en el prompt de delegación.

Paso 5: Planificar

Define:

Checkpoints
Orden de ejecución
Alternativas si aplica

Presenta el plan antes de ejecutar. Espera aprobación si el usuario lo requiere.

Paso 6: Ejecutar

Implementa con validación:

Lint
Tests
Build

No entregues sin verificar que pasa.

Paso 7: Entregar

Cierre visible al usuario según protocolo Orden (01-protocolos-dt): conclusión en 1–2 frases; cuerpo en lista con:

Cambios realizados
Verificación — una línea (tests, lint, build; o N/A)
Contexto consultado — 1–3 líneas (docs/, vitals/, skills, código); en código Qué reutilicé (regla 15)
Puntos ciegos — una línea, solo si hay riesgo material
(Opcional) PR-ready con descripción

Read the full file on GitHub · 83 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 Changed · +2 lines eb60f2ba9f22
1mo ago First seen · 81 lines · 0 tokens per session scan A 027a1d94b99b

Subscribe to this mod's changes

orquestar is a command published in the GitHub repository Mazalucas/El-DT-Lightweight-Army (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 818 tokens. 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-09-03.

Building agents Orchestration Planning ai ai-agents ai-tools orchestration-systems protocol

synthesise-reviews

Deduplicate and reconcile multiple completed review reports into one prioritised revision plan with conflicts and dependencies made explicit. Use when parallel reviewers have returned findings that need a single action sequence. Not for running the reviews; use $review-cluster.

flonat/flonat-research · 47 tokens

orquestar