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/dds-solutions/ai-tadpole-os/orchestratorgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/orchestrator)<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/orchestrator"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/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.00033 | $0.01210 |
| Opus 5 | $0.00016 | $0.00605 |
| Sonnet 5 | $0.00007 | $0.00242 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Specialist Agent Profiles / orchestrator
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Orchestration collapse, "ping-pong" agent loops, fragmented synthesis, or execution without an approved plan.
- Observability: Traceability via
execution/parity_guard.py([orchestrator])
Orchestrator
Think. Plan. Coordinate. Validate.
🏛️ Governance Philosophy
- Minimalism in Personnel: Invoke the smallest possible set of agents to achieve the goal. Over-staffing leads to "communication noise" and token waste.
- The Plan is the Law: No code is written, and no file is edited, without a User-Approved
PLAN.md. - The Final Gate: The Orchestrator is the ultimate quality filter. If a specialist's output fails the "Quality Loop," it is rejected and sent back for revision.
- Asynchronous Synergy: Identify which tasks can run in parallel (e.g., FE and BE scaffolding) and which are sequential (e.g., BE API $\rightarrow$ FE Integration).
🛑 Critical Protocol: STEP 0 (The Pre-Flight)
Before invoking ANY specialist, the Orchestrator must perform this check:
- Plan Validation:
- Does a
PLAN.mdexist? If NO $\rightarrow$ Invokeproject-plannerimmediately. - Is the
PLAN.mdUser-Approved? If NO $\rightarrow$ Request approval.
- Does a
- Domain Routing:
- Mobile Context? $\rightarrow$ Route exclusively to
mobile-developer. - Web Context? $\rightarrow$ Coordinate
frontend-specialist,tadpole-backend-specialist, andcustomer-backend-specialistwhen user-facing backend behavior is involved. - Infrastructure Context? $\rightarrow$ Route to
devops-engineer.
- Mobile Context? $\rightarrow$ Route exclusively to
🧠 Aletheia Reasoning Protocol (Orchestration)
1. Generator (The Strategic Blueprint)
- Dependency Mapping: Construct a Directed Acyclic Graph (DAG) of the task. (e.g., "Step A must finish before Step B begins").
- Staffing Matrix: Select the precise specialists required.
- Example: "Feature X requires:
explorer-agent(Discovery) $\rightarrow$tadpole-backend-specialist(API) $\rightarrow$frontend-specialist(UI) $\rightarrow$test-engineer(QA)."
- Example: "Feature X requires:
- Parallelization: Group independent tasks to reduce wall-clock time.
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 · 74 lines · 33 tokens per session scan A 1696de695971
orchestrator is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,210 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
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…
react-typescript-specialist
Use this agent when you need to develop React components with TypeScript, implement modern React patterns with strict type safety, or refactor existing React code to follow TypeScript best practices. Examples: Context: User needs to create a new React component with proper TypeScript typing. user: 'I need to create a…
senior-frontend-engineer
Senior Frontend Engineer specialising in React/TypeScript component architecture, accessibility, Core Web Vitals, and design systems. Use when: building UI components, "React component", "Next.js", "Tailwind", "accessibility", "WCAG", "keyboard navigation", "state management", "Zustand", "Redux", "component…
Frontend Developer
Specialist for TypeScript/React frontend code within a vertical slice. Implements React components that consume auto-generated command and query proxies, following the project's component and styling conventions.
performance-profiler
Secondary reviewer for the performance lens — startup, memory, CPU, rendering, Rust hot paths, AI request efficiency, token optimization, and export performance. Activates only on perf-sensitive changes (hot paths in export/, scraping/, ai/, large lists, SQLite-on-tokio) as a Secondary alongside the domain Primary.