NEWTON: Command for Claude Code

.claude/commands/run.md

run is a command for Claude Code from CUTEPKQ/NEWTON. It costs 32 tokens per session (734 once invoked), scanned A, original, MIT.

A command workflow for generating videos that show how objects behave under physics rules. It asks for a physical scenario, such as a marble rolling down a ramp, and runs the Newton video-generation process.

In plain words
What is it for?
Use it to generate a physics-based video from a described scenario, run a virtual physics experiment, or test what happens when objects interact.
Why use it?
It removes the need to check setup details and coordinate the generation steps by hand. It also identifies missing configuration before the process starts.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is CUTEPKQ/NEWTON's own configuration. It tells Claude Code how to work on NEWTON itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything NEWTON configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python loop/run_loop.py "<scenario>" --max-turns <N> --duration <D> --out-dir <dir>.

Reuse

Borrowing it

Nothing to install: this file belongs to CUTEPKQ/NEWTON. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/CUTEPKQ/NEWTON/main/.claude/commands/run.md
Clone the repo
git clone --depth 1 https://github.com/CUTEPKQ/NEWTON

Made for: Claude Code.

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 run

README.md
[![agentmods](https://agentmods.dev/badge/commands/cutepkq/newton/run/github.svg)](https://agentmods.dev/commands/cutepkq/newton/run)
Your own site
<a href="https://agentmods.dev/commands/cutepkq/newton/run"><img src="https://agentmods.dev/badge/commands/cutepkq/newton/run/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 run

Your own site · 80×15
<a href="https://agentmods.dev/commands/cutepkq/newton/run"><img src="https://agentmods.dev/badge/commands/cutepkq/newton/run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 734 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.00032 $0.00734
Opus 5.5 $0.00013 $0.00294
Sonnet 5.5 $0.00006 $0.00147
Haiku 4.5 $0.00003 $0.00073

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

Security

Grade A, and why

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

.claude/commands/run.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are helping the user run the Newton physics-video generation loop. Follow each step below.

Step 1 — Pre-flight checks

Verify the environment is ready:

  1. Check that .env exists in the project root. If not, tell the user to run /setup first.
  2. Scan .env for placeholder values (lines still containing <your-). Warn if any required keys are missing:
    • PLANNER_API_KEY and PLANNER_BASE_URL — required
    • SEEDANCE_API_KEY and SEEDANCE_HOST — required
    • Others are optional but enable more tools (tell the user which tools will be unavailable).
  3. Check that the newton conda environment is active. If not, activate it.

Step 2 — Scenario input

Ask the user: "What physics scenario do you want to generate?"

Encourage them to describe a concrete physical interaction — objects, materials, and what happens. Give a few examples to inspire them:

  • "A glass marble rolls down a wooden ramp and launches off the end"
  • "A water balloon drops onto a table and bursts"
  • "A pendulum swings and knocks over a row of dominoes"

Once they provide a description, help refine it if needed — the prompt should be specific about:

  • Object types and materials
  • Initial positions and motions
  • The key physical interaction (collision, deformation, fluid flow, etc.)
  • Expected outcome

Confirm the final scenario text with the user before proceeding.

Step 3 — Configure run options

Ask the user if they want to adjust any settings, or use defaults:

Flag Default Description
--max-turns 8 Maximum planner/executer/verifier rounds
--duration 5 Generated video length in seconds
--out-dir outputs/loop Output directory
--baseline (none) Path to an existing baseline mp4 to skip baseline generation

Most users should use the defaults. Only ask about these options once — don't repeat.

Step 4 — Run the loop

Execute the inference loop:

python loop/run_loop.py "<scenario>" --max-turns <N> --duration <D> --out-dir <dir>

Read the full file on GitHub · 76 lines

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 · 76 lines · 32 tokens per session scan A 2e907793da36

Subscribe to this mod's changes

run is a command published in the GitHub repository CUTEPKQ/NEWTON (139 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 734 once invoked, about $0.0001 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-30.

Related

run compared with commands from other repositories

run next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
runCUTEPKQ/NEWTONCommand1393mo agoMITA32Claude Code
READMEalirezarezvani/claude-skillsCommand29k3d agoMITA0Claude Code
spec-trace-requirementsrjmurillo/ai-agentsCommand49todayMITA0GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agentsCommand49todayMITA0GitHub Copilot
bootmicrosoft/PromptKitCommand11310d agoMITA14GitHub Copilot
relaysaajunaid/caddis-pluginCommand0yesterdayMITA12GitHub Copilot
hep-local.bodyagentlas-ai/Agentlas-OSCommand1.5ktodayApache-2.0A0Claude Code