design-fluid-scenes

design-fluid-scenes is a skill for Claude Code, Codex from wkzMagician/newton-mcp. It costs 56 tokens per session (380 once invoked), scanned A, original, Apache-2.0.

A guide for building computer simulations of smoke and liquid scenes, such as pouring water, splashes, and buoyant smoke.

In plain words
What is it for?
Use it to describe smoke or liquid volumes, emitters, walls, obstacles, gravity, wind, viscosity, surface tension, and preview runs before final rendering.
Why use it?
It provides rules for setting up fluid sources, containers, particle spacing, forces, and simulation settings without guessing how they fit together.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to describe smoke or liquid volumes, emitters, walls, obstacles, gravity, wind, viscosity, surface tension, and preview runs before final rendering.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wkzmagician/newton-mcp/design-fluid-scenes
Install

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.

Any agent
npx skills add wkzMagician/newton-mcp --skill design-fluid-scenes
Clone the repo
git clone --depth 1 https://github.com/wkzMagician/newton-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for design-fluid-scenes

README.md
[![agentmods](https://agentmods.dev/badge/skills/wkzmagician/newton-mcp/design-fluid-scenes/github.svg)](https://agentmods.dev/skills/wkzmagician/newton-mcp/design-fluid-scenes)
Your own site
<a href="https://agentmods.dev/skills/wkzmagician/newton-mcp/design-fluid-scenes"><img src="https://agentmods.dev/badge/skills/wkzmagician/newton-mcp/design-fluid-scenes/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.

agentmods 80×15 button for design-fluid-scenes

Your own site · 80×15
<a href="https://agentmods.dev/skills/wkzmagician/newton-mcp/design-fluid-scenes"><img src="https://agentmods.dev/badge/skills/wkzmagician/newton-mcp/design-fluid-scenes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 380 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.00380
Opus 5.5 $0.00022 $0.00152
Sonnet 5.5 $0.00011 $0.00076
Haiku 4.5 $0.00006 $0.00038

Measured 2mo ago against content hash ca433cbed0c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-fluid-scenes 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 2mo 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.

knowledge/skills/design-fluid-scenes/SKILL.md · 20 lines

What it actually says

Design fluid scenes

  1. Choose phase: smoke for a MAC-grid gas or phase: liquid for APIC/FLIP particles.
  2. Represent liquid initial volume with size and particle_spacing [m]; describe smoke sources with timed emitters.
  3. Use motion: static rigid bodies or container objects for floors, walls, and obstacles.
  4. Leave clearance of at least one particle spacing between fluid particles and container boundaries; use more clearance for fast rigid impacts.
  5. Use solver: auto; smoke routes to smoke and liquid routes to apic.
  6. Use uniform or radial fields for wind, attraction, repulsion, and other bulk effects.
  7. Estimate initial particles as volume / spacing^3; add emitter cross-section samples multiplied by active simulation substeps. For APIC adaptive resampling, also reserve roughly five particles per liquid grid cell. Capacity must cover the largest of these estimates.
  8. Prefer a short low-resolution validation run before a final render.

Specify liquid density, viscosity, surface tension, and flip_ratio, or smoke buoyancy and dissipation, directly in the scene IR.

Start smoke at 20--30 FPS and liquid at 20--25 FPS. Higher FLIP ratios preserve splash energy but need more boundary clearance; viscosity damps motion; smaller spacing increases particle count cubically. For pressure_nonconvergence, fix clearance and spacing before raising iterations. For capacity failures, increase spacing or shorten/narrow emission rather than continually raising capacity.

Changes

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.

  1. 2mo ago First seen · 20 lines · 56 tokens per session scan A ca433cbed0c5

Subscribe to this mod's changes

design-fluid-scenes is a skill published in the GitHub repository wkzMagician/newton-mcp (0 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 380 once invoked, about $0.0002 per session on Opus 5.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.

Related

design-fluid-scenes compared with skills from other repositories

design-fluid-scenes next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
design-fluid-sceneswkzMagician/newton-mcpSkill03mo agoApache-2.0A56Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill35kyesterdayApache-2.0A123Claude Code
matlabK-Dense-AI/scientific-agent-skillsSkill56k6d agoMITA44Claude Code
exploratory-data-analysisK-Dense-AI/scientific-agent-skillsSkill56k6d agoMITA83Claude Code
phylogeneticsK-Dense-AI/scientific-agent-skillsSkill56k6d agoMITA71Claude Code, Codex
research-engineerdavila7/claude-code-templatesSkill33ktodayMITA43Claude Code, Codex
mapping-to-snomedmaziyarpanahi/openmedSkill5.8ktodayApache-2.0A205Claude Code