Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add KumarSashank/motiscope/plugin install motiscopeWrote 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/kumarsashank/motiscope/recreate)<a href="https://agentmods.dev/skills/kumarsashank/motiscope/recreate"><img src="https://agentmods.dev/badge/skills/kumarsashank/motiscope/recreate.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.1 | $0.00075 | $0.01869 |
| Opus 5 | $0.00037 | $0.00934 |
| Sonnet 5 | $0.00015 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
recreate 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 9d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
motiscope: recreate
Translate a motiscope animation spec into real, runnable animation code for one target framework. Timing and easing come from the measured spec; you render it faithfully.
Resolve the plugin root
ROOT="${CLAUDE_PLUGIN_ROOT:-}"
[ -f "$ROOT/scripts/config.py" ] || ROOT="<absolute dir of this SKILL.md>/../.." # skills/recreate -> plugin root
SCRIPTS="$ROOT/scripts", REFS="$ROOT/references". On Windows use python for python3.
Step 1 — load the animation spec
- If
/motiscope:analyzejust produced a spec in this conversation, use it. - Otherwise locate the most recent analysis and read it:
ls -t .motiscope/*/manifest.json 2>/dev/null | head -1Readthatmanifest.json(and its siblingmotion.jsonfor the raw energy curve / segments). If there is none, run/motiscope:analyzefirst.
Step 2 — choose the target
- From
$1if given (gsap|css|framer|lottie). - Otherwise read the default and ask:
Ask the user (python3 "$SCRIPTS/config.py" # prints config incl. default_targetAskUserQuestion) to confirm the target (offer all four; default from config).
Then Read the target guide and the easing map:
Read "$REFS/easing-map.md"— maps each neutral ease token to a concrete value in every target.Read "$REFS/targets/<target>.md"— the rendering template for that target.Read "$REFS/measurement-traps.md"— if you are deriving any number yourself (a velocity, a parallax ratio, a period) rather than reading it fromreport.md.
Step 3 — generate the code
Split of responsibility (mirror the spec):
- Timing is measured — use it exactly.
start_ms,dur_ms, thebezier, staggereach_ms, loopperiod_mscome from motiscope's analysis; wire them verbatim (prefer the exactcubic-bezierover a named ease). - The effect is yours — build what the spec's
animationfield and the frames describe. You are not limited to opacity/translate/scale. If the animation is a mask/clip-path reveal, an SVG path draw, a morph, a 3D flip, a text split/typewriter, a blur or color shift, a parallax, a spring/physics bounce, or particles — build that directly in the target, going beyond the spec's simplepropswhen needed. Re-Readthe frames if you need to confirm the effect.
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.
- 9d ago First seen · 100 lines · 75 tokens per session scan A 50d9d9897413
recreate is a skill published in the GitHub repository KumarSashank/motiscope (112 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,869 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-30.
Other skills, from other repositories
remotion-to-hyperframes
Port an existing Remotion (React) composition's source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing Remotion mention, reference-only code, or "make something like my Remotion video" is a fresh build (/general-video). Unclear →…
hyperframes-animation
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4…
talking-head-recut
Package an existing talking-head / interview / podcast video with timed, designed GRAPHIC OVERLAY cards — kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture — synced to the transcript, on a 16:9 / 9:16 / 4:5 canvas of your choice; the clip plays untouched underneath. Trigger on…
embedded-captions
A workflow for adding captions or subtitles to an existing single-person talking-head video without changing the footage. Captions can appear as ordinary subtitles, behind the speaker, or as stylized visual effects.
faceless-explainer
Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a…
pr-to-video
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR…