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 skills/bananasjim/rdc-cli/_skillsnpx skills add BANANASJIM/rdc-cli --skill _skillsgit clone --depth 1 https://github.com/BANANASJIM/rdc-cliWrote 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/bananasjim/rdc-cli/_skills)<a href="https://agentmods.dev/skills/bananasjim/rdc-cli/_skills"><img src="https://agentmods.dev/badge/skills/bananasjim/rdc-cli/_skills.svg" alt="Measured on agentmods" 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 | $0.00082 | $0.03019 |
| Opus 5 | $0.00041 | $0.01510 |
| Sonnet 5 | $0.00016 | $0.00604 |
| Haiku 4.5 | $0.00008 | $0.00302 |
Grade A, and why
rdc-cli 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.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rdc-cli Skill
Overview
rdc-cli is a Unix-friendly command-line interface for RenderDoc GPU captures. It provides a daemon-backed architecture using JSON-RPC over TCP, a virtual filesystem (VFS) path namespace for navigating capture internals, and composable commands designed for shell pipelines, scripting, and CI assertions.
Install: pip install rdc-cli (requires a local RenderDoc build with Python bindings).
Check setup: rdc doctor.
Core Workflow
Follow this session lifecycle for any capture analysis task:
- Open a capture:
- Local:
rdc open path/to/capture.rdc - Remote replay (Proxy):
rdc open capture.rdc --proxy host:port - Split thin-client:
rdc open --connect host:port --token TOKEN - Android device:
rdc open capture.rdc --android [--serial SERIAL]
- Local:
- Inspect metadata:
rdc info,rdc stats,rdc events - Navigate the VFS:
rdc ls /,rdc ls /textures,rdc cat /draws/0/pipeline/summary - Analyze specifics:
rdc shaders,rdc pipeline,rdc resources,rdc bindings - Debug shaders:
rdc debug pixel EID X Y,rdc debug vertex EID VTXID,rdc debug thread EID GX GY GZ - Export data:
rdc texture ID -o out.png,rdc rt EID,rdc buffer ID -o buf.bin,rdc cbuffer EID --stage ps --binding 0,rdc log - Close the session:
rdc close
Session Management
- Default session name:
default(or value of$RDC_SESSION). - Override per-command:
rdc --session myname open capture.rdc. - Check active session:
rdc status. - Navigate to a specific event:
rdc goto EID.
Output Formats
All list/table commands default to TSV (tab-separated values) with a header row, suitable for cut, awk, and sort.
| Flag | Format | Use Case |
|---|---|---|
| (default) | TSV with header | Human reading, shell pipelines |
--no-header |
TSV without header | Piping to awk/cut without stripping |
--json |
JSON array | Structured processing with jq |
--jsonl |
Newline-delimited JSON | Streaming processing, large datasets |
-q / --quiet |
Minimal (single column) | Extracting IDs for loops |
What ships with it
2 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.
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.
- 4d ago First seen · 265 lines · 82 tokens per session scan A 1c3f65d9c922
rdc-cli is a skill published in the GitHub repository BANANASJIM/rdc-cli (167 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 3,019 once invoked, about $0.0004 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 skills, from other repositories
renderdoc-mcp
Analyze RenderDoc GPU frame captures with renderdoc-mcp MCP tools. Use when Codex needs to inspect .rdc captures, diagnose black screens or visual artifacts, explain frame structure, inspect specific draw calls, or investigate GPU rendering and performance issues.
phase2-adversarial-review
FloatSoda の Phase 2 完了時に、フェーズ全体のサーフェスを Codex に敵対的監査させるための /goal プロンプト群を生成する。finding は「再現する失敗テスト(red test)を添えたもの」だけを 受理する契約で、PR をまたぐ問題(ライフサイクル・差分更新・Flutter parity・Layer clone)を狙う。 「敵対的レビュー」「adversarial review」「フェーズ末の横断レビュー」「Phase2の総点検」 「PRをまたぐ問題を洗いたい」「red testで証明させたい」などの文脈で発火する。 個別 PR…
floatsoda-release
Drive a FloatSoda release end to end — pin the release scope against the previous tag and the Phase milestones, bump the version, finalize CHANGELOG (including the compare links that keep drifting), run the same verification CI runs, put the release through the junior-coder gate, then tag, watch the automated NuGet…
phase2-codex-goal
FloatSoda リポジトリの Phase 2(基礎ウィジェット量産)のリモート状況を調査し、 Codex に委任するための /goal プロンプトを生成する。 「Phase2の状況を見て」「Codexに次のタスクを流したい」「/goalのプロンプトを書いて」 「Phase2で次に何をやらせるべき?」など、Phase 2 の進捗確認や Codex への作業委任の 文脈が出たら必ずこのスキルを使うこと。明示的に FloatSoda と言われなくても、 Phase2 + Codex / リモート状況の組み合わせなら発火する。.
nebula-runtime
Control the live Nebula terminal workspace from Codex or Claude Code. Use whenever the user asks to split panes, open a tab or file, run a command in another pane, start or prompt Codex/Claude, delegate a task to another agent, read output, wait for an agent, or says 分屏、开一个 Codex/Claude、打开…
floatsoda-device-test
Run FloatSoda's device test — enumerate, with Codex, every scenario that can only break with SteamVR actually running plus every behavioural divergence from the Flutter port it mirrors, route each one to headless xunit or to the on-HMD harness, build that harness, have the owner run it in VR, and triage what falls…