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 skills add dcc-mcp/dcc-mcp-renderdoc --skill renderdoc-analysisgit clone --depth 1 https://github.com/dcc-mcp/dcc-mcp-renderdocWrote 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/skills/dcc-mcp/dcc-mcp-renderdoc/renderdoc-analysis)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-renderdoc/renderdoc-analysis"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-renderdoc/renderdoc-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-renderdoc/renderdoc-analysis"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-renderdoc/renderdoc-analysis.svg" alt="Reviewed on agentmods" width="80" 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.00208 | $0.03572 |
| Opus 5.5 | $0.00083 | $0.01429 |
| Sonnet 5.5 | $0.00042 | $0.00714 |
| Haiku 4.5 | $0.00021 | $0.00357 |
Grade A, and why
renderdoc-analysis 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 24d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RenderDoc Analysis
Inspect before exporting. These tools never modify the input .rdc; exports require an explicit
destination path and create its parent directory when needed.
Use export_drawcall_resources with an exact event ID to export only texture resources that the
pixel shader reports as used at that event. The result records binding, resource name, dimensions,
format, and output file for each PNG.
Inspection reports draw_dispatch_count, frame_work_count, present_count, and
frame_content_status so a structurally readable capture with no rendering work is not mistaken
for a usable frame.
Two capability tiers
This skill spans both RenderDoc backends, so check which one a tool needs before you call it:
| Tool | Backend | Answers |
|---|---|---|
inspect_capture |
renderdoccmd |
whether the file is structurally readable at all |
export_thumbnail, export_timeline, convert_capture |
renderdoccmd |
artifacts written to a path you name |
export_drawcall_resources |
renderdoc.pyd |
the textures one event actually used |
sample_pixel_region, diagnose_pixel_values |
renderdoc.pyd |
what the pixels in a region contain |
get_frame_overview |
renderdoc.pyd |
what the frame contains, in one replay |
get_draw_call_state |
renderdoc.pyd |
what one draw executed with |
analyze_render_passes |
renderdoc.pyd |
the pass structure and each pass's load, no counter needed |
analyze_state_changes |
renderdoc.pyd |
which state switches between adjacent draws were avoidable |
get_pass_timing |
renderdoc.pyd + a timing counter |
how long each pass took |
diff_draws |
renderdoc.pyd |
how much one target changed between two draws of one capture |
diff_captures |
renderdoc.pyd |
how much one target changed between two captures |
assert_pixels |
renderdoc.pyd |
whether that change stays inside thresholds, as a pass/fail verdict |
assert_state |
renderdoc.pyd |
whether two events' pipeline state matches, as a pass/fail verdict |
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- metadata/depends.md 19 B
- scripts/analyze_render_passes.py 1.5 KB runs code
- scripts/analyze_state_changes.py 1.6 KB runs code
- scripts/assert_pixels.py 5.0 KB runs code
- scripts/assert_state.py 3.0 KB runs code
- scripts/convert_capture.py 462 B runs code
- scripts/diagnose_pixel_values.py 2.4 KB runs code
- scripts/diff_captures.py 5.5 KB runs code
- scripts/diff_draws.py 5.0 KB runs code
- scripts/export_drawcall_resources.py 455 B runs code
- scripts/export_thumbnail.py 443 B runs code
- scripts/export_timeline.py 409 B runs code
- scripts/get_draw_call_state.py 1.5 KB runs code
- scripts/get_frame_overview.py 1.9 KB runs code
- scripts/get_pass_timing.py 1.9 KB runs code
- scripts/inspect_capture.py 446 B runs code
- scripts/sample_pixel_region.py 2.5 KB runs code
- tools.yaml 30 KB
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.
- 24d ago Changed · +103 lines · +47 tokens per session 5ef5448b1140
- 26d ago Changed · +80 lines · +111 tokens per session 7b77fcf48855
- 1mo ago First seen · 33 lines · 50 tokens per session scan A eeaf9a16dcdc
renderdoc-analysis is a skill published in the GitHub repository dcc-mcp/dcc-mcp-renderdoc (1 stars, last pushed today), licensed MIT. It adds 208 tokens to every session and 3,572 once invoked, about $0.0008 per session on Opus 5.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-31.
Other skills, from other repositories
performance-optimization
Find and fix game performance problems methodically — measure with the engine profiler first, reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix: object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets. Engine- neutral method that pairs with each…
beehave
Use when using the Beehave addon — pure-GDScript behavior trees with composites, decorators, leaves, a blackboard, and a visual runtime debugger.
godot-debugging
Use when debugging Godot projects — remote debugger, print techniques, signal tracing, common error patterns and fixes.
asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
hotfix
Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.
godot-development
Godot 4 reference patterns: signal-vs-call and physics-body decision tables, resource sharing traps, input handling, a common mistakes catalog, a GDScript to C# rosetta, typed class structure, pooling, autoloads, GUT tests, and collision layer constants. Use when designing, writing, or reviewing Godot 4 code.