process

A command that starts the EmbodiedGen workflow for scaling or rotating URDF-based 3D assets and their related files.

In plain words
What is it for?
Use it when you need to provide a URDF path, scale factor, and/or XYZ rotation, then report the command, output path, and applied transformations.
Why use it?
It turns a plain request into the appropriate processing command and makes the resulting output and operation mode clear.

Command

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.

agentmods
npx agentmods add commands/horizonrobotics/embodiedgen/process
Clone the repo
git clone --depth 1 https://github.com/HorizonRobotics/EmbodiedGen
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 188 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.00188
Opus 5 $0.00006 $0.00094
Sonnet 5 $0.00003 $0.00038
Haiku 4.5 $0.00001 $0.00019

Measured 2d ago against content hash 6a74355a5ff8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

embodied_gen/skills/claude_plugin/plugins/embodiedgen/commands/process.md · 33 lines

What it actually says

Process Skill Command

Route the user's request to the EmbodiedGen asset processing workflow.

Workflow

Step 1: Interpret the request

Use $ARGUMENTS if provided. If it is empty, ask for the URDF path and desired scale factor and/or XYZ rotation in degrees.

Step 2: Load the skill

Use skill: "embodiedgen:asset-process".

Step 3: Execute the workflow

Follow the skill and build the correct python -m embodied_gen.skills.asset-process.asset_process command.

Step 4: Deliver

Return:

  1. The exact command used
  2. The output path
  3. Whether the operation is normal mode or inplace mode
  4. The applied scale factor and XYZ rotation
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. 2d ago First seen · 33 lines · 13 tokens per session scan A 6a74355a5ff8

Subscribe to this mod's changes

process is a command published in the GitHub repository HorizonRobotics/EmbodiedGen (648 stars, last pushed 9d ago), licensed Apache-2.0. It adds 13 tokens to every session and 188 once invoked, about $0.0001 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.