mux-audit

Audit multiplexed protocol implementations for frame parsing, flow control, and stream lifecycle defects.

5|1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/Hatedatastructures/Prism --skill mux-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mux-audit
Source: https://github.com/Hatedatastructures/Prism/tree/main/.claude/skills/mux-audit
Command: npx skills add https://github.com/Hatedatastructures/Prism --skill mux-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps review multiplexed protocol code for correctness and security issues that are easy to miss in manual inspection, especially in proxy systems that carry many logical streams over one connection.

Core Features & Use Cases

  • Frame Parsing Review: Checks length validation, buffer boundaries, and unknown frame handling to prevent crashes and memory corruption.
  • Flow-Control Safety: Examines window updates for underflow and overflow risks, plus concurrency races in credit accounting.
  • Stream Lifecycle Auditing: Verifies stream ID allocation, half-close semantics, FIN handling, and idempotent shutdown behavior.
  • Library Integration Checks: Reviews settings negotiation, GOAWAY emission, and external HTTP/2 or mux library options for protocol compliance.
  • Use Case: A proxy engine maintainer can use this Skill before shipping a new mux transport to catch protocol violations, resource leaks, and shutdown bugs.

Quick Start

Use mux-audit to inspect the multiplexed transport implementation and flag unsafe frame handling, flow-control errors, and stream lifecycle bugs.

Frequently Asked Questions about mux-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit HTTP/2 frame parsing for buffer boundary and memory corruption risks?

Auditing HTTP/2 frame parsing involves checking length validation, buffer boundaries, and unknown frame handling to prevent crashes and memory corruption in multiplexed protocol implementations.

What causes flow-control underflow or overflow in multiplexed proxy engines?

Flow-control underflow or overflow in multiplexed proxy engines stems from unsafe window updates and concurrency races in credit accounting that require careful examination to prevent errors.

How do I verify stream lifecycle and half-close semantics in a custom mux layer?

Verifying stream lifecycle in a custom mux layer requires checking stream ID allocation, half-close semantics, FIN handling, and idempotent shutdown behavior to ensure correct resource management.

Does mux-audit work with external HTTP/2 library integration and settings negotiation?

Mux-audit works with external HTTP/2 library integration by reviewing settings negotiation, GOAWAY emission, and library options to verify protocol compliance and safe shutdown behavior.

What is the best way to catch protocol violations before shipping a new mux transport?

The best way to catch protocol violations before shipping a new mux transport is to inspect the multiplexed implementation for unsafe frame handling, flow-control errors, and stream lifecycle bugs.

When do I need to check GOAWAY emission and stream ID atomicity in proxy security?

You need to check GOAWAY emission and stream ID atomicity in proxy security when reviewing multiplexed protocol code for compliance, boundary checks, and shutdown safety defects before release.