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/mintdotgg/mint-threejs-skills/threejs-debug-profilernpx skills add mintdotgg/mint-threejs-skills --skill threejs-debug-profilergit clone --depth 1 https://github.com/mintdotgg/mint-threejs-skillsWrote 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/mintdotgg/mint-threejs-skills/threejs-debug-profiler)<a href="https://agentmods.dev/skills/mintdotgg/mint-threejs-skills/threejs-debug-profiler"><img src="https://agentmods.dev/badge/skills/mintdotgg/mint-threejs-skills/threejs-debug-profiler.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.00035 | $0.00386 |
| Opus 5 | $0.00017 | $0.00193 |
| Sonnet 5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
threejs-debug-profiler 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 5d 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
Three.js Debug Profiler
Find the owning cause or measured bottleneck before changing code.
Read references/debug-profile-checklists.md for the applicable render,
runtime, loading, mobile, audio, physics, or performance path.
Debug Workflow
- Reproduce in the correct build mode.
- Read the first console, page, and relevant network errors.
- Check canvas display/drawing-buffer size, renderer/context, and loop ownership.
- Check camera, clipping, lights, fog, materials, visibility, transforms, and scene contents.
- Check asset paths, loaders, CORS, base path, async ordering, and Mint artifact integration.
- Check delta units, update order, fixed timestep, bodies/colliders, listeners, pointer/touch behavior, resize, and audio unlock/decode.
- Fix the cause in the owning module.
- Retest the broken path plus screenshot, canvas pixels, and errors.
Performance Workflow
- Record target device, viewport, DPR, build mode, and worst-case scenario.
- Measure frame time/FPS, draw calls, triangles, resources, memory, bundle, and expensive shadows/shaders/post-processing.
- Identify CPU, GPU, memory, or network ownership.
- Change one bottleneck at a time using reuse, instancing, culling, LOD, pooling, disposal, DPR limits, or cheaper rendering.
- Re-measure the same scenario and verify playability and visuals.
Final Response
Lead with root cause or bottleneck. Report files changed, baseline/post metrics, commands, screenshots/artifacts, retested paths, and residual risks.
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.
- 5d ago First seen · 41 lines · 35 tokens per session scan A 3ac3a0dce6b6
threejs-debug-profiler is a skill published in the GitHub repository mintdotgg/mint-threejs-skills (110 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 386 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…