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/tmhsdigital/unity-developer-tools/render-pipeline-detectionnpx skills add TMHSDigital/Unity-Developer-Tools --skill render-pipeline-detectiongit clone --depth 1 https://github.com/TMHSDigital/Unity-Developer-ToolsWhat 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.00027 | $0.01131 |
| Opus 5 | $0.00014 | $0.00566 |
| Sonnet 5 | $0.00005 | $0.00226 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
render-pipeline-detection 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 157 lines · 27 tokens per session scan A 6c1d73c91ab6
render-pipeline-detection is a skill published in the GitHub repository TMHSDigital/Unity-Developer-Tools (3 stars, last pushed 17d ago), with no licence file. It adds 27 tokens to every session and 1,131 once invoked, about $0.0001 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-31.
Other skills, from other repositories
unity
Operational skill for Claude to automate Unity Editor/runtime with C# scripts, EditorWindow tools, Addressables, URP/HDRP, and CLI batch builds.
unity-reviewer
Use after implementation to review code changes for Unity anti-patterns, performance issues, and correctness problems. Also use when superpowers:requesting-code-review is active to provide Unity-specific review criteria.
component-design
Use when you need detailed decision frameworks for MonoBehaviour composition, inter-component communication, single responsibility, and execution order.
data-modeling
Use when you need detailed decision frameworks for ScriptableObject patterns, runtime data management, serialization strategies, and data-driven architecture.
prefab-architecture
Use when you need detailed decision frameworks for prefab vs variant vs ScriptableObject, nested prefab design, override strategies, and prefab editing workflows.
scene-architecture
Use when you need detailed decision frameworks for scene structure, additive loading, scene management, transitions, and persistent managers.