p4-implement-team-orchestrator

p4-implement-team-orchestrator is an agent for Claude Code from babyworm/rtl-agent-team. It costs 46 tokens per session (4,940 once invoked), scanned A, original, MIT.

An orchestrator is an agent that coordinates other agents. This one manages a ten-wave pipeline for implementing RTL, or register-transfer-level hardware code, with work split by module and dependencies between waves.

In plain words
What is it for?
It is for managing multi-module RTL implementation across parallel teams and dependency stages.
Why use it?
It reduces the effort of coordinating parallel hardware implementation work and keeping dependent tasks in order.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; names the AskUserQuestion tool; mentions Codex.

Part of the rtl-agent-team plugin — 47 skills, 99 agents, 6 hooks shipped together

Good fit It is for managing multi-module RTL implementation across parallel teams and dependency stages.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/babyworm/rtl-agent-team/p4-implement-team-orchestrator
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/babyworm/rtl-agent-team

Made for: Claude Code.

Or install rtl-agent-team, the plugin that ships this one along with the rest of its 47 skills, 99 agents, 6 hooks.

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.

agentmods badge for p4-implement-team-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p4-implement-team-orchestrator/github.svg)](https://agentmods.dev/agents/babyworm/rtl-agent-team/p4-implement-team-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p4-implement-team-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p4-implement-team-orchestrator/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.

agentmods 80×15 button for p4-implement-team-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p4-implement-team-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p4-implement-team-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,940 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.04940
Opus 5 $0.00023 $0.02470
Sonnet 5 $0.00009 $0.00988
Haiku 4.5 $0.00005 $0.00494

Measured 9d ago against content hash bb969fb807ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

p4-implement-team-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 9d 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.

agents/p4-implement-team-orchestrator.md · 334 lines

How it starts

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

RAT audit protocol (condensed; dev source: plugin_docs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime):

  • Tag key moments [RAT: CATEGORY | SOURCE] description — categories: THOUGHT, DECISION (source label MANDATORY), INSIGHT, DELEGATE (name the target agent), WARNING (specific, actionable).
  • DECISION source labels: USER_CONFIRMED | SPEC_DERIVED (cite section) | AGENT_ASSUMED (brief justification required). Tag natural decision points only — do not over-annotate routine operations.
  • Prompt self-report: on spawn, save your received task description to .rat/audit/{session_id}/prompts/{NNN}_{agent-name}.md ({session_id} from .rat/audit/session-id.txt); skip silently if the audit dir is absent.
  • Path convention: {plugin_root} in any path = plugin installation root, read from .rat/state/spawn-context.json field plugin_root; if unavailable, try the project-local path, else proceed without the file. Resolve project-relative paths against PROJECT_ROOT=<abs> (prompt) > spawn-context project_root > $RAT_PROJECT_ROOT env > CWD.

You are the Phase 4 RTL Implementation Team Orchestrator. You manage the 10-wave RTL implementation pipeline using task-based coordination for parallel execution across modules and waves.

The rtl-p4-implement-policy skill (loaded via skills: field) defines all wave criteria, coding conventions, overlap rules, escalation conditions, and checklists.

Coordination Teammate Role (MANDATORY)

You are a coordination teammate, spawned via Agent(team_name=...). The skill (main session) created the team and spawned you alongside workers. You coordinate via TaskCreate/TaskList/TaskUpdate and direct workers via SendMessage.

FORBIDDEN: TeamCreate, TeamDelete, Agent(team_name=...) ALLOWED: TaskCreate, TaskList, TaskUpdate, SendMessage, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion

SendMessage Usage

  • Direct workers: Send task clarification, priority changes, or context to specific workers
  • Broadcast updates: Notify all workers of task graph changes or blocking issues
  • Report to leader: Send progress summaries and completion status to the leader
  • Signal completion: Notify the leader ONLY after the phase gate AND all post-gate mandatory steps (compliance check, ADR generation, phase summary, Codex cross-review) have passed — NOT when the task graph merely drains.

Read the full file on GitHub · 334 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.

  1. 9d ago First seen · 334 lines · 46 tokens per session scan A bb969fb807ab

Subscribe to this mod's changes

p4-implement-team-orchestrator is an agent published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 15d ago), licensed MIT. It adds 46 tokens to every session and 4,940 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-30.