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 svd-ai-lab/sim-cli --skill workbenchgit clone --depth 1 https://github.com/svd-ai-lab/sim-cliWrote 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/svd-ai-lab/sim-cli/workbench)<a href="https://agentmods.dev/skills/svd-ai-lab/sim-cli/workbench"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/workbench/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/svd-ai-lab/sim-cli/workbench"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/workbench.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.00070 | $0.01355 |
| Opus 5.5 | $0.00028 | $0.00542 |
| Sonnet 5.5 | $0.00014 | $0.00271 |
| Haiku 4.5 | $0.00007 | $0.00136 |
Grade A, and why
workbench-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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- workbench-sim — 88% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workbench-sim
You are connected to Ansys Workbench via sim-cli. This file is the index. It tells you where to look for actual content — it does not contain the content itself.
The /connect response told you which active layers apply via:
"skills": {
"root": "<sim-skills>/workbench",
"active_sdk_layer": "0.4",
"active_solver_layer": "24.1"
}
Always read the index for base/, then your active sdk/<version>/,
then your active solver/<version>/. Later layers override earlier
ones on identically-named files.
base/ — always relevant
Concepts, API patterns, and version-agnostic reference:
| Path | What's there |
|---|---|
base/reference/pyworkbench_api.md |
PyWorkbench SDK API surface: launch_workbench, run_script_string, upload_file, download_file, start_mechanical_server, start_fluent_server. Read first. |
base/reference/journal_scripting.md |
IronPython .wbjn scripting reference: SetScriptVersion, GetTemplate, CreateSystem, GetContainer, and the result file convention. |
base/reference/system_templates.md |
Live template discovery and resolver workflow. Template names are product/configuration dependent; treat any examples as non-authoritative. |
base/reference/file_transfer.md |
File upload/download patterns between client and server. |
base/reference/sub_solver_integration.md |
Starting PyMechanical, PyFluent, PySherlock servers from within a Workbench session. |
base/snippets/ |
Numbered IronPython journal snippets (01 through 05). Each writes results to %TEMP%/sim_wb_result.json. |
base/examples/ |
Official PyWorkbench examples from pyansys.com — Fluent workflow, PyMechanical integration, logging, cooled turbine blade, cyclic symmetry, axisymmetric rotor, material designer. |
base/workflows/static_structural/ |
Validation guidance for Static Structural workflows. Use the API reference and snippets to build the intended project. |
base/workflows/project_review_loop.md |
Required checkpoint loop: inspect health, project identity, systems summary, then run one bounded journal step. |
base/workflows/debug_failed_exec.md |
Failure triage loop for failed Workbench snippets and RunWB2 journals. |
base/workflows/mechanical_handoff.md |
Workbench-to-Mechanical checklist for Static Structural workflows. |
base/known_issues.md |
Vendor quirks, SDK version constraints, IronPython limitations. |
What ships with it
26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- base/examples/advanced_examples_index.md 749 B
- base/examples/axisymmetric_rotor.md 4.3 KB
- base/examples/cooled_turbine_blade.md 4.4 KB
- base/examples/cyclic_symmetry_analysis.md 6.0 KB
- base/examples/fluent_workflow.md 2.5 KB
- base/examples/logging.md 3.0 KB
- base/examples/material_designer_workflow.md 2.8 KB
- base/examples/pymechanical_integration.md 4.1 KB
- base/known_issues.md 5.8 KB
- base/reference/file_transfer.md 1.8 KB
- base/reference/journal_scripting.md 2.7 KB
- base/reference/pyworkbench_api.md 4.1 KB
- base/reference/sub_solver_integration.md 2.2 KB
- base/reference/system_templates.md 2.1 KB
- base/snippets/01_smoke_test.py 411 B runs code
- base/snippets/02_create_static_structural.py 869 B runs code
- base/snippets/04_run_journal.py 890 B runs code
- base/snippets/05_file_transfer.py 846 B runs code
- base/workflows/debug_failed_exec.md 2.5 KB
- base/workflows/mechanical_handoff.md 1.3 KB
- base/workflows/project_review_loop.md 2.0 KB
- base/workflows/static_structural/evidence/README.md 374 B
- base/workflows/static_structural/README.md 374 B
- sdk/0.10/notes.md 1.2 KB
- sdk/0.4/notes.md 947 B
- solver/24.1/notes.md 1014 B
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.
- 2d ago First seen · 106 lines · 70 tokens per session scan A 7d4a3d814901
workbench-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 70 tokens to every session and 1,355 once invoked, about $0.0003 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.
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.
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…
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.
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…
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, 응력…
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…