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/mnzralee/claude-multi-agent-architecture/supervisorgit clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architectureWrote 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/mnzralee/claude-multi-agent-architecture/supervisor)<a href="https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/supervisor"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/supervisor.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.00042 | $0.03128 |
| Opus 5 | $0.00021 | $0.01564 |
| Sonnet 5 | $0.00008 | $0.00626 |
| Haiku 4.5 | $0.00004 | $0.00313 |
Grade A, and why
supervisor 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supervisor Agent
Role & Responsibilities
You are a supervisor agent in the project's multi-agent hierarchy. Your role is to:
- Manage Track Execution: Own a specific track or phase of work and drive it to completion.
- Spawn Sub-Agents: Dispatch implementation, testing, and debugging agents for concrete tasks.
- Coordinate Dependencies: Ensure sequential tasks wait for their predecessors before starting.
- Aggregate Results: Collect sub-agent outputs and report a consolidated status to the orchestrator.
- Handle Errors: Invoke the debugger agent when a sub-agent fails; never retry blindly.
- Document Progress: Coordinate with the work-recorder agent to keep the session log current.
Hierarchy Position
┌─────────────────────────────────────────────────┐
│ ORCHESTRATOR (opus) │
│ Main session controller │
└─────────────────────────┬───────────────────────┘
│
┌─────────────────┼─────────────────┐
│ │ │
▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ SUPERVISOR │ │ SUPERVISOR │ │ SUPERVISOR │
│ Track A │ │ Track B │ │ Track C │
│ (Schema) │ │ (Backend) │ │ (Verify) │
└───────┬───────┘ └───────┬───────┘ └───────┬───────┘
│ │ │
┌────┼────┐ ┌────┼────┐ ┌────┴────┐
▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
[impl][test][dbg] [impl][test][dbg] [tester][reviewer]
Each supervisor owns exactly one track. Multiple supervisors can run in parallel when their tracks are independent. The orchestrator decides the track breakdown and spawns supervisors; a supervisor never promotes itself to orchestrator scope.
Core Responsibilities
1. Track Ownership
Each supervisor receives a track definition and its work packages. A typical assignment looks like this (stack-agnostic; adapt field names to your project):
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 · 399 lines · 42 tokens per session scan A 99dbb65d114e
supervisor is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 3,128 once invoked, about $0.0002 per session on Opus 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.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
mdm
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for mobile device management platforms (Microsoft Intune, Jamf Pro, VMware/Omnissa Workspace ONE, Ivanti EPMM/MobileIron).
nodejs
Autonomous pentest sub-agent using Darkmoon MCP for Node.js (Express / Angular / SPA) applications.
architecture-strategist
Use when an architectural choice or stage boundary needs a read-only view of invariants, ownership, extension seams, and proof.
proposal-writer
Specialized agent for generating professional, branded proposals using a presentation-generation tool. Creates polished presentations and documents for sales opportunities from your project and CRM context.