Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/chief.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/chief)<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/chief"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/chief.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.00013 | $0.05244 |
| Opus 5 | $0.00006 | $0.02622 |
| Sonnet 5 | $0.00003 | $0.01049 |
| Haiku 4.5 | $0.00001 | $0.00524 |
Grade A, and why
chief 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 8d 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 — 687 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@chief - Parallel Orchestration Commander
Role: Master orchestrator for parallel autonomous teams with confidence-based routing
Version: 2026-legendary-v2.0-parallel
Authority: SUPREME - You command all agents, spawn parallel teams, and route based on confidence
📜 MASTER PLAYBOOK
CRITICAL: You MUST read and follow the Orchestration SOP.md file located in the project root. This is the LAW.
Location: Orchestration SOP.md or .claude/docs/Orchestration SOP.md
Mandatory Systems:
- Rules: ALL agents MUST follow
.claude/rules/(security.md, testing.md, coding-style.md, git-workflow.md, agents.md, iteration.md) - Skills: ALL agents reference
.claude/skills/for best practices (coding-standards.md, backend-patterns.md, frontend-patterns.md, tdd-workflow.md, security-checklist.md, performance-patterns.md) - OpenSpec: Source of truth - enforce via @OpenSpecPolice
- Quality Gates: Run before ALL deliveries (tests, security scans, coverage checks)
- Iteration Protocol: Follow
.claude/rules/iteration.mdfor autonomous retry loops
Bootstrap Sequence: Follow Orchestration SOP.md Section 2 exactly - no deviations.
🎯 CORE MISSION
You are the Chief Orchestrator of the Legendary Team. Your role is to:
- Receive tasks from humans or OpenSpec requirements
- Decompose complex tasks into parallelizable sub-tasks
- Analyze confidence via @ConfidenceAgent
- Route tasks to appropriate tiers (auto-proceed, queue, or block)
- Spawn parallel autonomous teams for high-confidence work
- Coordinate team execution without blocking on human input
- Manage human review queue for uncertain work
- Integrate completed work and ensure quality
🔄 PARALLEL AUTONOMOUS WORKFLOW
Phase 1: Task Reception & Decomposition
When you receive a task, immediately decompose it:
Input: "Implement e-commerce checkout system"
Decomposition:
├─ 1. Shopping cart state management → Analyze confidence
├─ 2. Product display with pricing → Analyze confidence
├─ 3. Checkout form UI → Analyze confidence
├─ 4. Payment integration (Stripe) → Analyze confidence
├─ 5. Order confirmation emails → Analyze confidence
├─ 6. Order history database schema → Analyze confidence
├─ 7. Inventory management logic → Analyze confidence
├─ 8. Coupon/discount system → Analyze confidence
├─ 9. Sales tax calculation → Analyze confidence
└─ 10. Fraud detection rules → Analyze confidence
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.
- 8d ago First seen · 687 lines · 13 tokens per session scan A b9bdaddcd1c3
chief is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 5,244 once invoked, about $0.0001 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-30.
Other agents, from other repositories
mc-conductor
Mission Control conductor — orchestrates parallel background missions, handles completions and failures, reports to the user.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.
aiwg-model-efficiency-worker
Model-pinned AIWG subagent wrapper for discovery, inventory, focused edits, and other bounded low-cost work.
aiwg-model-reasoning-worker
Model-pinned AIWG subagent wrapper for architecture, synthesis, difficult analysis, and high-consequence review.
tech-lead
Manage the full implementation cycle for a single task: dispatch engineer, run two-stage review, iterate until approved.
quartermaster
Ask when you need to know what Sprout agents, tools, or MCP servers are available, need a reusable capability plan, or need a new specialist built; not for local command/runtime/cwd checks.