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.
git clone --depth 1 https://github.com/babyworm/rtl-agent-teamWrote 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/p4s-bugfix-orchestrator)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p4s-bugfix-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p4s-bugfix-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.
<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p4s-bugfix-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p4s-bugfix-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.02224 |
| Opus 5 | $0.00026 | $0.01112 |
| Sonnet 5 | $0.00010 | $0.00445 |
| Haiku 4.5 | $0.00005 | $0.00222 |
Grade A, and why
p4s-bugfix-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.
How it starts
The opening of the file, as written. The whole thing — 191 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 the RTL Bug Fix Orchestrator. You drive the complete bug fix cycle ensuring every RTL change is functionally verified — not just lint-checked.
Your job is to ANALYZE the bug, DELEGATE fix+lint to rtl-coder, DELEGATE TB creation to testbench-dev, DELEGATE simulation to eda-runner, and MANAGE parallel UNIT_FIX when multiple independent modules fail. You do NOT write RTL or testbenches yourself.
The rtl-p4s-bugfix-policy skill (loaded via skills: field) defines the mandatory 4-step sequence, parallel fix decision tree, escalation rules, and checklist.
Workflow
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).
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.
- 9d ago First seen · 191 lines · 52 tokens per session scan A 773cabceec0a
p4s-bugfix-orchestrator is an agent published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 15d ago), licensed MIT. It adds 52 tokens to every session and 2,224 once invoked, about $0.0003 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
neuron-nki-debugger-agent
Use this agent for autonomously debugging and fixing NKI kernel compilation errors. This agent analyzes compiler errors, searches for fixes in documentation and code examples, applies corrections following the principle of simplicity over performance, and validates the fixes. Context: User has a kernel with…
tdmcp-implementation-runtime-analyst
Studies the lived runtime path of a completed tdmcp implementation: TouchDesigner bridge behavior, hardware setup, diagnostics, calibration, audio/video/projector issues, latency, and user-facing operator ergonomics.
jetson-perf-investigator
Diagnose Jetson performance and memory issues end to end. Captures a baseline, isolates the dominant consumer, and recommends concrete next actions by orchestrating the Jetson Platform Skills catalog. Use when the user reports "Jetson is slow / hot / OOM" without a clear cause.
analyzer
MANDATORY AGENT FOR ROOT CAUSE ANALYSIS, SYSTEM DESIGN, CODE REVIEW, AND DEAD-END DIAGNOSTICS. SPECIFIC TRIGGERS: (1) RCA: developer reported an error or tester failed an Assert — trace call chain, find exact broken file:line locally via Ripgrep / AST; (2) pre-code analysis: call BEFORE developer when task needs…
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
Demonstrate
Agent for demonstrating VS Code features.