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 playcanvas/create-playcanvas --skill inspect-runtimegit clone --depth 1 https://github.com/playcanvas/create-playcanvasWrote 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/playcanvas/create-playcanvas/inspect-runtime)<a href="https://agentmods.dev/skills/playcanvas/create-playcanvas/inspect-runtime"><img src="https://agentmods.dev/badge/skills/playcanvas/create-playcanvas/inspect-runtime/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/playcanvas/create-playcanvas/inspect-runtime"><img src="https://agentmods.dev/badge/skills/playcanvas/create-playcanvas/inspect-runtime.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.00030 | $0.00525 |
| Opus 5.5 | $0.00012 | $0.00210 |
| Sonnet 5.5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
inspect-runtime 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 14d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- inspect-runtime — 100% identical, 0 lines differ
What it actually says
Inspect a running app
From Engine 2.23, every app announces itself to a hook at
globalThis[Symbol.for('playcanvas.inspector')]. Read live state through it instead of adding
window.app or debug code to the app.
Attach
- Resolve
scripts/devtools-hook.jsrelative to this skill and inject it as an init script that runs before any page script. A hook defined later misses existing apps; reload instead. - Page code then reads
globalThis.__playcanvasApps, aMapfrom each live app to{ version, revision, protocol }.app.init()adds the entry andapp.destroy()removes it. - The script chains a hook defined before it, such as a devtools extension's.
- No entry means the Engine predates 2.23, the hook loaded late, or the app set
devtools: false. The Engine swallows errors thrown by the hook. - In 2.23.0 only the debug build (
playcanvas/debug,build/playcanvas.dbg.*) announces apps; the default import never calls the hook. Later 2.23 patches fix every build.
Read state
- Read after
frameend, so values reflect a rendered frame. - Return plain numbers and strings to the caller, not Engine objects.
- Useful reads:
app.root.findByName()andfindByTag(), world positions andmeshInstance.aabb,app.stats.drawCallCountandframeTime, andentity.anim.baseLayer.activeState. - Pause with
app.timeScale = 0;updatestill runs with a zerodt. Step one frame by restoring the scale, then zeroing it again on the nextframeend. - Revert anything you change to take a measurement.
Inspector panel
@playcanvas/inspector adds a panel for people: new Inspector(app) shows the hierarchy, assets,
materials, shaders, textures, render targets, frame graph, and physics. It must import the app's
own playcanvas package, so add it only to development builds. It draws over the canvas and
applies view overrides, so destroy it before verify-pixels captures. Stepping through draws
needs the debug build.
What ships with it
1 file 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.
- 14d ago First seen · 42 lines · 30 tokens per session scan A 024613c39acb
inspect-runtime is a skill published in the GitHub repository playcanvas/create-playcanvas (60 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 525 once invoked, about $0.0001 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-10-02.
Other skills, from other repositories
cli-anything-nsight-graphics
Windows-first CLI harness for Nsight Graphics capture, GPU Trace summary, and ngfx-replay analysis.
minecraft-debug-mcp
Operate and debug the live Minecraft bot through its built-in MCP REPL server. Use when work requires starting the bot with pnpm dev, connecting to the local MCP endpoint, inspecting cognitive state/logs/history, injecting synthetic chat/events, or running targeted REPL code against the running brain during…
unity-console
Capture and query the Unity Editor console.
diagnosing-bgs-problems
A symptom-first guide for investigating crashes, frame-rate drops, stuttering, freezes, and startup failures in Bethesda Game Studios games with mods.
axiom-audit-spritekit
Use when the user wants to audit SpriteKit game code for common issues — physics bitmask issues, draw call waste, node accumulation, and action leaks.
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…