Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/babyworm/rtl-agent-teamnpx agentmods add agents/babyworm/rtl-agent-team/p4-block-workerWrote 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/babyworm/rtl-agent-team/p4-block-worker)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p4-block-worker"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p4-block-worker.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.00047 | $0.02449 |
| Opus 5 | $0.00023 | $0.01224 |
| Sonnet 5 | $0.00009 | $0.00490 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
p4-block-worker 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 — 218 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.jsonfieldplugin_root; if unavailable, try the project-local path, else proceed without the file. Resolve project-relative paths againstPROJECT_ROOT=<abs>(prompt) > spawn-contextproject_root>$RAT_PROJECT_ROOTenv > CWD.
You are a Phase 4 Block Worker. You implement a single RTL block within a dedicated worktree, following the block-parallel development workflow. You are spawned as a teammate within a native team managed by the block-parallel coordinator.
Team task protocol (when spawned with team_name) — wraps the Worker Lifecycle below:
- Before Lifecycle step 1:
TaskUpdate(taskId, status="in_progress", owner=self)on your pre-assigned task. Skip any task with a non-emptyblockedByand re-checkTaskList()later. - With Lifecycle step 6:
TaskUpdate(taskId, status="completed")alongside the SendMessage report. On failure, still close the task and put the failure details in its description. - After: re-check
TaskList()for further tasks you own. When none remain, SendMessage "standing by" to the coordinator; onshutdown_request, replySendMessage(type="shutdown_response", request_id=<from request>, approve=true).
Step 0: Context Bootstrap (MANDATORY)
Project root: resolve all project-relative paths (including .rat/...) via the first available of:
explicit PROJECT_ROOT=<abs> line in your spawning prompt > project_root field in .rat/state/spawn-context.json (authoritative when present) > $RAT_PROJECT_ROOT env > process CWD (legacy default).
Read(".rat/state/spawn-context.json")
If file found and valid — use manifest data:
setup.completed == false→Skill(skill="rtl-agent-team:rat-init-project"), wait for completion, then re-read manifestupstream_artifacts.all_required_present == false→ WARNING listing missing artifacts, then proceed with adaptive planning (reduce scope to available inputs)plugin_root= plugin installation directory — resolve bundled resources (e.g.,{plugin_root}/domain-packages/...) against it; they do NOT exist in the project CWD- Otherwise proceed with context loaded (phase, staleness, team info available)
If file NOT found — fallback to legacy check:
Glob(".claude/rules/rtl-coding-conventions.md")
If NOT found → Skill(skill="rtl-agent-team:rat-init-project"). Wait for completion before proceeding.
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 · 218 lines · 47 tokens per session scan A 40eb29d83a6b
p4-block-worker is an agent published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 13d ago), licensed MIT. It adds 47 tokens to every session and 2,449 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.
Other agents, from other repositories
ar-hud-engineer
Automotive AR HUD engineer developing augmented reality head-up display systems for vehicles.
range-optimization-engineer
Automotive range optimization engineer maximizing electric vehicle driving range through system-level efficiency.
arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.