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 wkzMagician/newton-mcp --skill orchestrate-animation-scenegit clone --depth 1 https://github.com/wkzMagician/newton-mcpWrote 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/wkzmagician/newton-mcp/orchestrate-animation-scene)<a href="https://agentmods.dev/skills/wkzmagician/newton-mcp/orchestrate-animation-scene"><img src="https://agentmods.dev/badge/skills/wkzmagician/newton-mcp/orchestrate-animation-scene/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/wkzmagician/newton-mcp/orchestrate-animation-scene"><img src="https://agentmods.dev/badge/skills/wkzmagician/newton-mcp/orchestrate-animation-scene.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.00032 | $0.00386 |
| Opus 5 | $0.00016 | $0.00193 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
orchestrate-animation-scene 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 11d 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
Orchestrate an animation scene
- Translate the prompt only into supported schema-version-2 IR primitives; do not generate Warp kernels.
- Check structured resource budgets before preview. Perform at most three repair rounds. Each round is
apply_scene_patch,validate_scene, thenpreview_scene. - Repair only diagnostics tied to the requested outcome. Do not silently simplify away contacts, fluids, constraints, or motion.
- Keep preview limits separate from the stored IR: one second, 640 by 360 pixels, reduced fluid grids, and at most 50,000 liquid particles.
- Once validation and preview metrics are credible, call
run_scene(scene_name, output_dir). - Poll
get_joband inspect its stage, frame progress, diagnostics, and artifact paths. Usecancel_jobonly when the requested job should stop. Poll only while status isqueuedorrunning;completed,failed,physics_failed,cancelled, andinterruptedare terminal. - Treat a render failure as a render-stage problem when
cache/manifest.jsonis complete; reuse the cache instead of repeating simulation. - Deliver
animation.mp4,scene.json,program.py,metrics.json,diagnostics.jsonl, andcache/together.
In each repair round, change one category of parameters only. Do not treat steadily increasing resolution, substeps, iterations, particle capacity, or grid size as a repair strategy. Address resource errors by reducing the dominant metric; address energy failures by reducing forcing/stiffness; address deformation failures by reducing impact and balancing damping; address pressure failures by fixing boundary clearance and particle spacing.
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.
- 11d ago First seen · 19 lines · 32 tokens per session scan A 8e5671492784
orchestrate-animation-scene is a skill published in the GitHub repository wkzMagician/newton-mcp (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 32 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-31.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…