shader-ir

Parse HLSL, GLSL, and SPIR-V to detect suspicious shader fingerprints.

15|5|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill shader-ir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shader-ir
Source: https://github.com/haolange/RDC-Agent-Frameworks/tree/main/debugger/platforms/claude-code/.claude/skills/shader-ir
Command: npx skills add https://github.com/haolange/RDC-Agent-Frameworks --skill shader-ir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a specialist capability to analyze shader source code and intermediate representations (IR), surface suspicious fingerprints, and guide safe, broker-mediated investigation workflows for GPU rendering artifacts.

Core Features & Use Cases

  • Shader and IR parsing: Extract tokens, control flow, and data-flow indicators from HLSL, GLSL, and SPIR-V disassembled IR.
  • Fingerprint detection: Identify suspicious patterns, obfuscation techniques, anomalous instructions, and potential exploit indicators within shader code and IR evidence.
  • Operational safety & orchestration: Enforce staged handoff, broker-mediated runtime access, and intake gate checks to prevent unsafe live interactions.
  • Use Case: Triage a renderer crash or suspected malicious shader by correlating shader source, compiled IR, and runtime artifacts to prioritize investigative actions.

Quick Start

Ask the shader-ir specialist to analyze the attached shader files and IR traces for suspicious constructs and provide a prioritized list of findings.

Frequently Asked Questions about shader-ir

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

FAQPage Schema
How do I detect suspicious fingerprints in SPIR-V or GLSL shader code?

To detect suspicious fingerprints in shader code, parse HLSL, GLSL, or SPIR-V text to extract control-flow and data-flow indicators. This analysis identifies obfuscation techniques, anomalous instructions, and potential exploit indicators within the shader source.

What is the best way to investigate malicious shader behavior during a GPU rendering crash?

Investigate malicious shader behavior by correlating shader source, compiled intermediate representation, and runtime artifacts. This staged handoff workflow prioritizes investigative actions to triage renderer crashes and identify potential vulnerabilities safely.

Can I analyze disassembled SPIR-V intermediate representation for potential vulnerabilities?

Yes, you can analyze disassembled SPIR-V intermediate representation to extract tokens and identify potential vulnerabilities. The analysis surfaces suspicious patterns and anomalous instructions within the IR evidence to guide investigative actions.

How do I enforce operational safety when debugging GPU rendering issues with live runtime access?

Enforce operational safety when debugging GPU rendering issues by applying broker-mediated runtime access and intake gate checks. This prevents unsafe live interactions during the investigation of shader artifacts and intermediate representations.

Does shader analysis work with HLSL, GLSL, and SPIR-V formats?

Yes, shader analysis works with HLSL, GLSL, and SPIR-V text or disassembled intermediate representation. It parses these formats to extract control-flow and data-flow indicators for detecting suspicious fingerprints and exploit indicators.