mechanical-sim

mechanical-sim is a skill for Claude Code, Codex from svd-ai-lab/sim-cli. It costs 143 tokens per session (1,893 once invoked), scanned A, original, Apache-2.0.

A guide for using Ansys Mechanical, an engineering program that applies loads and boundary conditions, solves structural or other physics models, and reports results. It also explains how to read solved result files.

In plain words
What is it for?
Editing model setup, defining loads and boundary conditions, running solves, inspecting results, and reading solved .rst result files.
Why use it?
It keeps project orchestration in Workbench separate from model setup and solving in Mechanical. This reduces the risk of sending commands to the wrong Ansys tool and supports evidence-based result checks.

Skill for Claude CodeCodex

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

Good fit Editing model setup, defining loads and boundary conditions, running solves, inspecting results, and reading solved .rst result files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/svd-ai-lab/sim-cli/mechanical
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 svd-ai-lab/sim-cli --skill mechanical
Clone the repo
git clone --depth 1 https://github.com/svd-ai-lab/sim-cli

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 mechanical-sim

README.md
[![agentmods](https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/mechanical/github.svg)](https://agentmods.dev/skills/svd-ai-lab/sim-cli/mechanical)
Your own site
<a href="https://agentmods.dev/skills/svd-ai-lab/sim-cli/mechanical"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/mechanical/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 mechanical-sim

Your own site · 80×15
<a href="https://agentmods.dev/skills/svd-ai-lab/sim-cli/mechanical"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/mechanical.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 143 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,893 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.00143 $0.01893
Opus 5.5 $0.00057 $0.00757
Sonnet 5.5 $0.00029 $0.00379
Haiku 4.5 $0.00014 $0.00189

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

Security

Grade A, and why

mechanical-sim 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.

The scan reads SKILL.md. This mod also ships 6 executable files (base/snippets/01_smoke.py, base/snippets/02_list_project_tree.py, base/snippets/03_add_fixed_support.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/mechanical/src/sim_plugin_mechanical/_skills/mechanical/SKILL.md · 138 lines

How it starts

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

mechanical-sim

This file is the Ansys Mechanical index. Use DPF for solved .rst files on disk; use sim-cli/PyMechanical for live Mechanical sessions that mutate, solve, inspect, or update the GUI-backed project.

This is not the Abaqus plugin. Do not run Abaqus .inp decks or Abaqus/CAE scripts here. Use solver=abaqus for Dassault SIMULIA Abaqus; use solver=mechanical only for Ansys Mechanical / PyMechanical sessions.

The /connect response tells you which active layers apply:

"skills": {
  "root":               "<sim-skills>/mechanical",
  "active_sdk_layer":   "0.12",
  "active_solver_layer": "24.1"
}

Always read base/, then your active sdk/<version>/, then your active solver/<version>/. Later layers override earlier ones on identically-named files.


First principles

  1. Workbench orchestrates, Mechanical computes. PyWorkbench drives Engineering Data / Geometry / Model. PyMechanical drives Setup / Solution / Results. Do not try to define boundary conditions via Workbench scripting — that belongs here.

  2. Observation is SDK+GUI coupled. Every uv run sim exec is a mechanical.run_python_script(code) call that mutates Mechanical's in-memory model. Mechanical's window on the desktop redraws after each call. Therefore uv run sim screenshot (which grabs the desktop) always reflects the current SDK state. This coupling only works with batch=False — so the driver defaults to GUI mode. Confirm both ui_mode == "gui" and batch == false from inspect session.summary before relying on screenshots for GUI sync.

  3. Scripts run inside Mechanical's IronPython interpreter. Globals ExtAPI, DataModel, Model, Quantity, Tree are already available — do NOT import ansys.mechanical. The last expression's string form is what run_python_script returns, so end snippets with a json.dumps(...) literal to get structured output.

  4. ExtAPI.DataModel.Project is the root. From there: .Model → the scene; .Model.Analyses[0] → the first analysis; .Model.Geometry → bodies; .Model.Mesh → meshing controls; .Model.Materials → material assignments.

Read the full file on GitHub · 138 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. 2d ago First seen · 138 lines · 143 tokens per session scan A 8d050555bb04

Subscribe to this mod's changes

mechanical-sim is a skill published in the GitHub repository svd-ai-lab/sim-cli (239 stars, last pushed yesterday), licensed Apache-2.0. It adds 143 tokens to every session and 1,893 once invoked, about $0.0006 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-10-19.

Related

Other skills, from other repositories

openfoam-sim

Use when the user asks Codex, Claude Code, or another AI coding agent to run, inspect, or debug OpenFOAM cases through sim-cli. Supports case checks, solver execution, log inspection, result artifacts, replayable CFD workflows, and benchmark tasks.

svd-ai-lab/sim-plugin-openfoam · 58 tokens

abaqus-sim

Use when the user asks Codex, Claude Code, ChatGPT-style coding agents, or another AI agent to automate, inspect, run, or debug Abaqus through sim-cli. Supports Abaqus/CAE noGUI workflows, batch jobs, model inspection, ODB diagnostics, bounded execution, artifact reporting, and troubleshooting. Requires a user-owned…

svd-ai-lab/sim-plugin-abaqus · 77 tokens

omnisim-world-builder

Build, inspect, run, and debug OmniSim robotics worlds through the first-party MCP tools. Use for requests involving OmniSim scenes, robots, cameras, contacts, physics checks, or screenshots; do not use for unrelated simulators.

omnilink-tech/omnisim · 53 tokens

cae-postprocess

CAE simulation post-processing translator skill. Translates natural language requests from CFD/FEA/SPH domain experts into viznoir MCP tool calls. Provides domain vocabulary mapping (50+ terms in Korean/English), data-driven visualization idea generation from inspectdata results, and cinematic-first aesthetic guidance…

kimimgo/viznoir · 165 tokens

fea-workflow

FEA post-processing workflow skill. Guides AI agents through finite element analysis visualization: stress distribution, deformation, mode shapes, and yield detection. Maps FEA domain vocabulary to viznoir MCP tool calls. Triggers: FEA, structural, stress, deformation, displacement, von Mises, yield, mode shape, 응력…

kimimgo/viznoir · 81 tokens

sph-workflow

SPH/DualSPHysics post-processing workflow skill. Guides AI agents through particle method visualization: fluid filtering, sloshing animations, isosurface mesh extraction, and particle distribution analysis. Maps SPH domain vocabulary to viznoir MCP tool calls. Triggers: SPH, DualSPHysics, particles, sloshing, fluid…

kimimgo/viznoir · 91 tokens