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.
npx agentmods add instructions/rudybear/renderdoc-skill/claude-mdgit clone --depth 1 https://github.com/rudybear/renderdoc-skillWhat 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 | $0.00464 | $0.00464 |
| Opus 5 | $0.00232 | $0.00232 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
renderdoc-skill CLAUDE.md 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 3d 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.
What it actually says
RenderDoc + Claude Code GPU Debugging
Project Overview
This project wires Claude Code to RenderDoc via rdc-cli, enabling automated GPU frame capture, inspection, and debugging for Vulkan/D3D/GL applications.
Tools
- rdc-cli (
rdc): 66-command CLI wrapping RenderDoc's Python API. Installed viapip install rdc-cli. - renderdoc.pyd: Python module from RenderDoc (built from source or from an official install).
Environment
RENDERDOC_PYTHON_PATH=<path-to-renderdoc-module>— rdc-cli uses this to find renderdoc.pyd- Captures go in
./captures/(or any directory you choose) - Analysis exports (PNGs, meshes, buffers) go in
./captures/analysis/
Your Application (customize this section)
- Executable:
/path/to/your/app - CWD requirement: Set CWD to your project root if the app resolves assets relative to CWD
- Debug markers: List any debug markers your app emits (e.g., "Shadow Pass", "GBuffer Pass")
- Scenes / modes: List any flags or scenes relevant to your app
Capture Requirements
- Vulkan layer: Must be registered (see README.md for setup)
- Environment:
ENABLE_VULKAN_RENDERDOC_CAPTURE=1must be set for Vulkan apps - Swapchain: The app must present frames (headless apps without
vkQueuePresentKHRcannot be captured) - Capture script: See
capture_frame.pyfor an example using the RenderDoc Python API directly
Quick Start
# Check setup
rdc doctor
# Capture a frame (adapt the capture script for your app)
python capture_frame.py
# Inspect
rdc open ./captures/my_capture.rdc
rdc info --json
rdc draws --limit 20
rdc close
GPU Debugging Skill
See .claude/skills/renderdoc-gpu-debug/SKILL.md for the full GPU debugging skill with workflows, recipes, and command reference.
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.
- 3d ago First seen · 52 lines · 464 tokens per session scan A 136040b3eb7d
renderdoc-skill CLAUDE.md is an instructions file published in the GitHub repository rudybear/renderdoc-skill (202 stars, last pushed 6mo ago), licensed MIT. It adds 464 tokens to every session, about $0.0023 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.