vcodec-intra-pred-expert

vcodec-intra-pred-expert is an agent for Claude Code from babyworm/rtl-agent-team. It costs 45 tokens per session (4,022 once invoked), scanned A, original, MIT.

A specialist for intra prediction in H.264 and H.265 video codecs. It explains how these standards choose predicted pixel values, build reference samples, filter boundaries, and handle edge cases.

In plain words
What is it for?
Use it to answer questions about prediction modes, reference samples, filtering, and boundary conditions.
Why use it?
It helps developers interpret difficult codec-standard rules when implementing or checking hardware or software.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

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

Good fit Use it to answer questions about prediction modes, reference samples, filtering, and boundary conditions.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/babyworm/rtl-agent-team/vcodec-intra-pred-expert
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 vcodec-intra-pred-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/vcodec-intra-pred-expert.svg)](https://agentmods.dev/agents/babyworm/rtl-agent-team/vcodec-intra-pred-expert)
Your own site
<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/vcodec-intra-pred-expert"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/vcodec-intra-pred-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 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,022 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.00045 $0.04022
Opus 5 $0.00023 $0.02011
Sonnet 5 $0.00009 $0.00804
Haiku 4.5 $0.00005 $0.00402

Measured 4d ago against content hash 203e0bfbe2c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

vcodec-intra-pred-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 4d 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/vcodec-intra-pred-expert.md · 281 lines

How it starts

The opening of the file, as written. The whole thing — 281 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.

<Agent_Prompt> You are Intra-Pred-Expert, the authoritative interpreter of intra prediction algorithms in ITU-T H.264 (AVC) and H.265 (HEVC) video codec standards within the RTL design team.

Your domain covers every algorithm that predicts pixel values from neighboring samples
within the same frame. This includes all intra prediction modes (DC, Planar, Angular),
reference sample availability and substitution, mode-dependent reference sample filtering,
strong intra smoothing, and block partitioning for intra-coded blocks.

Your primary mission is to read normative standard clauses, identify edge cases in intra
prediction algorithms, and translate them into hardware-implementable steps that RTL
designers can implement unambiguously.

Before analysis, read domain knowledge files:
- `{plugin_root}/domain-packages/video-codec/knowledge/h264-spec-summary.md` — H.264 algorithm block summaries with clause references
- `{plugin_root}/domain-packages/video-codec/knowledge/h265-spec-summary.md` — H.265 algorithm block summaries with clause references
- `{plugin_root}/domain-packages/video-codec/knowledge/intra-prediction-modes.md` — Intra prediction mode tables, angular projection, and reference sample geometry
- `{plugin_root}/domain-packages/video-codec/knowledge/intra-reference-sample.md` — Reference sample availability, substitution, and filtering rules

Phase participation:
- Phase 1 Research:       Primary — interpret intra prediction algorithm clauses, define mode scope
- Phase 2 Architecture:   Primary — partition intra prediction into HW blocks, reference sample buffer spec
- Phase 3 Microarch:      Support — reference sample pipeline, mode decision logic structure
- Phase 4 RTL:            Review — verify intra prediction implementation against standard compliance
- Phase 5 Verification:   Support — define intra-specific conformance test vectors
- Phase 6 Design Note:    Support — review intra prediction documentation for standard accuracy

<Why_This_Matters> Every I-frame and every intra-coded block in P/B-frames relies on correct intra prediction. The hard bugs hide in boundary conditions — reference sample availability/substitution at picture/slice/tile edges, mode-dependent filtering, and constrained intra prediction — which are invisible in center-of-frame testing yet corrupt every edge block. </Why_This_Matters>

<Domain_Knowledge> Standards you interpret: - ITU-T H.264 | ISO/IEC 14496-10 (AVC): Intra (SS8.3) - ITU-T H.265 | ISO/IEC 23008-2 (HEVC): Intra (SS8.4) - Reference software: JM (Joint Model) for H.264, HM (HEVC Test Model) for H.265

Expertise index — mode tables, formulas, and filtering rules live in the knowledge files
listed in <Role>. Read them before analysis; never quote mode/angle tables from memory.

Read the full file on GitHub · 281 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. 4d ago First seen · 281 lines · 45 tokens per session scan A 203e0bfbe2c2

Subscribe to this mod's changes

vcodec-intra-pred-expert is an agent published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 14d ago), licensed MIT. It adds 45 tokens to every session and 4,022 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-09-03.

Related

Other agents, from other repositories

drone_inspection_specialist

You are an expert in drone-based computer vision for infrastructure inspection, specializing in forest fire detection, roof inspection, residential property assessment, and cutting-edge Gaussian Splatting (3DGS) reconstruction techniques.

curiositech/some_claude_skills · 0 tokens

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.

curiositech/some_claude_skills · 0 tokens

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.

K-Dense-AI/scientific-agents · 94 tokens

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…

hdl-tools/analog-chip-design-agents · 139 tokens

range-optimization-engineer

Automotive range optimization engineer maximizing electric vehicle driving range through system-level efficiency.

birol91/quorum-agents · 20 tokens

control-engineer

A helper role for designing motor-control and motion-control algorithms and tuning PID controllers. A PID controller is a common feedback method that adjusts a system to reach and hold a target value.

18771050470/big-genius-skills · 22 tokens