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/tu11aa/squadrant/explainer-reelnpx skills add tu11aa/squadrant --skill explainer-reelgit clone --depth 1 https://github.com/tu11aa/squadrantWrote 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/tu11aa/squadrant/explainer-reel)<a href="https://agentmods.dev/skills/tu11aa/squadrant/explainer-reel"><img src="https://agentmods.dev/badge/skills/tu11aa/squadrant/explainer-reel.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.00174 | $0.02420 |
| Opus 5 | $0.00087 | $0.01210 |
| Sonnet 5 | $0.00035 | $0.00484 |
| Haiku 4.5 | $0.00017 | $0.00242 |
Grade A, and why
explainer-reel 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 3d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
explainer-reel
Two output modes for explaining a structure/system/flow with motion or interactivity, instead of a static diagram:
| Mode | Output | Use when |
|---|---|---|
reel (default) |
a short, looping animated GIF — dark-neon, thin monoline, terminal-panel chrome | the ask is a passive, embeddable loop (e.g. "how JWT auth works" as a <img> in docs) |
interactive |
a self-contained interactive HTML page — dark IBM Plex dev-console theme, horizontal system bands, click-node detail panel, tabs | the ask is to explore who-calls-whom across systems (e.g. "map this request across three services") |
Both modes are wrap-the-engine, build-the-style-pack — see provenance below. Pick the mode
from the user's ask; default to reel when the request is ambiguous (issue #598's original scope
and golden reference are reel mode).
Provenance:
mode=reelwrapsiart-ai/explainer-video-skills(the engine — motion primitives + a verify-loop toolkit) with a squadrant style-pack (design tokens + component library + a GIF pipeline the engine doesn't ship).mode=interactivewrapsvisual-explainer'sgenerate-web-diagram(the engine for self-contained interactive HTML) with a named swimlane preset (bands/particles/detail-panel layout grammar) so that command doesn't reinvent the layout each time.
See docs/specs/2026-07-23-animated-system-graph-skill.md (issue #598, addendum for the two-mode
scope) for the full build-vs-buy rationale. Don't rebuild either engine's techniques from
scratch — reuse them; this skill only supplies the style/preset layer on top.
When to use this vs. plain visual-explainer
- Plain
visual-explainer— static or entrance-only diagrams (one-shot reveal on load), or an interactive diagram with no particular bands/swimlane shape. Use for most architecture docs, plans, and diagrams. explainer-reelmode=reel— continuous, looping motion is the explicit ask: a packet traveling a path, a counter climbing, a verify/reject beat.explainer-reelmode=interactive— the ask specifically wants bands = systems with network-hop edges and flow-particles (a "swimlane" system-flow map), not a general diagram.
What ships with it
12 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.
- assets/scene-kit.js 8.5 KB runs code
- assets/swimlane-preset.html 22 KB
- assets/theme.css 3.3 KB
- examples/jwt-reel.gif 336 KB
- examples/jwt-reel.html 11 KB
- references/component-library.md 4.6 KB
- references/design-tokens.md 3.9 KB
- references/interactive-mode.md 4.3 KB
- scripts/contact-sheet.sh 1.0 KB runs code
- scripts/README.md 1.7 KB
- scripts/render-gif.sh 2.2 KB runs code
- scripts/seek-shot.sh 1.3 KB runs code
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.
- 3d ago First seen · 161 lines · 174 tokens per session scan A 633b9acead05
explainer-reel is a skill published in the GitHub repository tu11aa/squadrant (2 stars, last pushed 3d ago), licensed MIT. It adds 174 tokens to every session and 2,420 once invoked, about $0.0009 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…