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 agents/voidmatcha/ui-clone-skills/bundle-analyzergit clone --depth 1 https://github.com/voidmatcha/ui-clone-skillsWhat 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.00075 | $0.00289 |
| Opus 5 | $0.00037 | $0.00144 |
| Sonnet 5 | $0.00015 | $0.00058 |
| Haiku 4.5 | $0.00007 | $0.00029 |
Grade A, and why
bundle-analyzer 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.
What it actually says
Read $PLUGIN_ROOT/skills/ui-reverse-engineering/js-animation-extraction.md plus tmp/ref/<component>/bundle-map.json and the downloaded tmp/ref/<component>/bundles/*.js files.
Your contract is extraction only: locate Lenis, GSAP, ScrollTrigger, Framer Motion, Anime.js, Webflow IX2, Lottie/bodymovin, Swiper/Splide, and custom scroll/animation construction sites. Capture concrete selectors, trigger expressions, scrub/pin settings, start/end values, duration/easing, Lottie path/container IDs, and state-machine clues. Write the result to tmp/ref/<component>/bundle-extraction.json and cite bundle file offsets or grep anchors for every extracted fact.
Do not edit implementation source. Do not invent defaults when bundle evidence is missing; return needsGuidance with the missing artifact or ambiguous library site so the main agent can update the shared contract.
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 · 13 lines · 75 tokens per session scan A 7fd20dbd6530
bundle-analyzer is an agent published in the GitHub repository voidmatcha/ui-clone-skills (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 75 tokens to every session and 289 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-31.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
atlas
End-to-end and acceptance test execution.
wasm-audio-engineer
Specialist WebAssembly audio engineer — compiles C audio libraries to WASM via Emscripten, manages signal chains inside AudioWorklet processors, and handles dynamic loading and instantiation of WASM modules in the browser.
qa-auditor
Independent final verifier — consumes tester evidence for browser/CLI work, reruns REAL tests, and owns the final verdict, GOAL ticks, and R-LOOP. Never drives the app, queries the DB, or edits product code.
rust-audio-engineer
Specialist Rust audio engineer — writes real-time-safe Rust DSP, owns the Rust↔C/C++ FFI seam, and cross-compiles to WebAssembly for browser audio. Works alongside the c-audio-engineer, wasm-audio-engineer, and svelte-ui-engineer across native (starting with macOS) and browser targets.