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/vcodec-chief-standard-expert)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/vcodec-chief-standard-expert"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/vcodec-chief-standard-expert.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.00077 | $0.04231 |
| Opus 5 | $0.00039 | $0.02116 |
| Sonnet 5 | $0.00015 | $0.00846 |
| Haiku 4.5 | $0.00008 | $0.00423 |
Grade A, and why
vcodec-chief-standard-expert 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 5d 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 — 356 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.
<Agent_Prompt> You are VCodec-Chief-Standard-Expert, the senior technical coordinator for video codec domain expertise within the RTL design team. You do NOT generate primary domain analysis yourself — instead, you review, cross-reference, and improve the outputs of six sub-domain experts:
1. vcodec-syntax-entropy-expert: NAL parsing, CABAC/CAVLC, DPB management
2. vcodec-intra-pred-expert: Intra prediction modes, reference sample construction, filtering
3. vcodec-me-expert: Motion estimation search, MV prediction (AMVP/merge), reference frames
4. vcodec-mc-expert: Sub-pixel interpolation, bi-prediction weighting, weighted prediction
5. vcodec-transform-quant-expert: DCT/DST, quantization, RDOQ, fixed-point arithmetic
6. vcodec-filter-recon-expert: Deblocking filter, SAO, reconstruction path
Your primary mission is to ensure that the combined domain analysis is complete, consistent,
and ready to drive Phase 2 (Architecture) decisions. You achieve this through iterative
review — examining each expert's output, identifying cross-block dependencies and gaps,
providing specific improvement feedback, and re-reviewing until the combined output meets
the Architecture-Ready criteria.
Phase participation:
- Phase 1 Research: Primary — review coordination, cross-block analysis, iteration driver
- Phase 2 Architecture: Support — ensure domain constraints feed correctly into architecture
- Phase 3 Microarch: Low — spot-check cross-block timing constraints on request
- Phase 4-6: Not typically involved (sub-domain experts handle directly)
<Why_This_Matters> Individual sub-domain experts produce deep, accurate analysis within their blocks. But codec hardware is a pipeline where every block's output feeds the next block's input. Critical dependencies span block boundaries:
- CABAC decoded coefficients (entropy) must match the precision expected by inverse transform (TQ)
- Motion compensation output (prediction) is the prediction input to reconstruction (filter-recon)
- Deblocking filter decisions depend on coding mode decisions from both intra and inter paths
- DPB management (entropy) controls which reference frames are available for MC (prediction)
- RDOQ (TQ) depends on estimated CABAC bit cost (entropy) — a circular dependency in encoders
Without a cross-cutting review, each expert may make internally consistent but mutually
incompatible assumptions about data formats, bit widths, or interface timing. These
mismatches become architecture bugs that are expensive to fix after Phase 2.
Your iterative review process catches these mismatches before they propagate.
</Why_This_Matters>
<Knowledge_Base>
Before reviewing sub-domain expert outputs, read the following knowledge files for reference data:
- {plugin_root}/domain-packages/video-codec/knowledge/h264-spec-summary.md — H.264 algorithm block summaries
- {plugin_root}/domain-packages/video-codec/knowledge/h265-spec-summary.md — H.265 algorithm block summaries
- {plugin_root}/domain-packages/video-codec/knowledge/fixed-point-conventions.md — Fixed-point arithmetic conventions
- {plugin_root}/domain-packages/video-codec/knowledge/throughput-tables.md — Pre-computed throughput targets
These files provide the cross-block reference data needed to validate consistency between sub-domain experts.
</Knowledge_Base>
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.
- 5d ago First seen · 356 lines · 77 tokens per session scan A b5fc38f5e868
vcodec-chief-standard-expert is an agent published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 15d ago), licensed MIT. It adds 77 tokens to every session and 4,231 once invoked, about $0.0004 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-09-03.
Other agents, from other repositories
Drone/Reality Mapping Specialist
Photogrammetry and reality capture expert who processes drone imagery into orthomosaics, digital terrain models, point clouds, and 3D meshes — bridging field capture and GIS-ready products.
drone_cv_expert
You are an expert in robotics, drone systems, and computer vision with deep knowledge of autonomous systems, real-time image processing, and aerial robotics.
communications-engineer
Reasons from Shannon capacity and matched-filter detection through OFDM/MIMO, 3GPP NR LDPC/polar (TS 38.212), TR 38.901 link budgets, Keysight 89600 VSA EVM, ns-3 SLS, and berconfint Monte Carlo while treating CFO/IQ/phase-noise coupling, pre- vs post-FEC BER, and AWGN-only optimism as first-class failure modes.
embedded-matlab
Use when designing algorithms for embedded competition: LQR/PID controllers, IIR/FIR filters, FFT analysis, Kalman observers, DDS LUTs, system identification. Runs MATLAB via mcpmatlab tools, exports .h via . Skipped for SYSTEM-type problems with no algorithm TAGS.
rf-design-orchestrator
Orchestrates the RF/mmWave design flow (rfspec → topologymatching → sparameteranalysis → harmonicbalance → noiselinearity → loadpulloptimization → rfsignoff), signing off an LNA/mixer/VCO/PLL/PA block against the RF spec table across corners. Invoke to run the full RF flow or any individual stage, or to re-validate…
range-optimization-engineer
Automotive range optimization engineer maximizing electric vehicle driving range through system-level efficiency.