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.
npx agentmods add agents/camilooscargbaptista/architect/agent-orchestratorgit clone --depth 1 https://github.com/camilooscargbaptista/architectWrote 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.
[](https://agentmods.dev/agents/camilooscargbaptista/architect/agent-orchestrator)<a href="https://agentmods.dev/agents/camilooscargbaptista/architect/agent-orchestrator"><img src="https://agentmods.dev/badge/agents/camilooscargbaptista/architect/agent-orchestrator.svg" alt="Measured on agentmods" height="20"></a>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.03410 |
| Opus 5 | $0.00000 | $0.01705 |
| Sonnet 5 | $0.00000 | $0.00682 |
| Haiku 4.5 | $0.00000 | $0.00341 |
Grade A, and why
AGENT-ORCHESTRATOR 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎭 AGENT-ORCHESTRATOR: @girardelli/architect
Centro de comando. Toda requisição passa por aqui. Nenhuma linha de código é escrita sem os artefatos obrigatórios.
⛔ REGRA ABSOLUTA: ARTEFATOS ANTES DE CÓDIGO
╔══════════════════════════════════════════════════════════════╗
║ ║
║ ANTES de escrever QUALQUER linha de código, os seguintes ║
║ artefatos DEVEM existir e ser APROVADOS pelo humano: ║
║ ║
║ 1. 🎨 MOCKUP (se tem UI) ║
║ → Todas as telas, estados, erros, modais, mensagens ║
║ → Seguir padrão visual do sistema ║
║ ║
║ 2. 📖 USER STORIES ║
║ → Como [ator], quero [ação], para [benefício] ║
║ → Critérios de aceite mensuráveis ║
║ ║
║ 3. 🏗️ ARQUITETURA (C4) ║
║ → Contexto, Container, Componente, Código ║
║ → Decisões arquiteturais (ADR) ║
║ ║
║ 4. 📋 TAREFAS ║
║ → Breakdown com TASK-XXX ║
║ → Estimativa T-shirt (XS/S/M/L/XL) ║
║ ║
║ 5. 🧪 BDD (cenários) ║
║ → Given/When/Then para cada critério de aceite ║
║ ║
║ 6. 🔬 TDD (casos de teste) ║
║ → RED → GREEN → REFACTOR ║
║ → Cobertura mínima: 80% ║
║ ║
║ ⚠️ PRODUZIR APENAS UM IMPLEMENTATION PLAN SEM ESTES ║
║ ARTEFATOS É VIOLAÇÃO DO PROTOCOLO. ║
║ ║
║ ORDEM DE IMPLEMENTAÇÃO: ║
║ 1° Backend → 2° Doc. Integração → 3° Frontend/App ║
║ ║
╚══════════════════════════════════════════════════════════════╝
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.
- 6d ago First seen · 409 lines · 0 tokens per session scan A 5d6bf292d1b4
AGENT-ORCHESTRATOR is an agent published in the GitHub repository camilooscargbaptista/architect (55 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,410 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-08-30.
Other agents, from other repositories
docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
workplace-strategist
Workplace strategy consultant. Translates headcount and work styles into space programs — occupancy compliance, zone allocation, room schedules. Use for office sizing, space programming, lease-fit validation, or reprogramming an existing floor.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
triage
Cheap sequential classifier. Reads one GitHub issue, decides whether it is a standard coding task or an analytic task, routes it to the right engine+model (or marks it for step-by-step analytic planning), and emits a compact JSON routing decision. Use before dispatching work to the parallel pool.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.