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-plugin-comsol --skill comsolgit clone --depth 1 https://github.com/svd-ai-lab/sim-plugin-comsolWrote 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-plugin-comsol/comsol)<a href="https://agentmods.dev/skills/svd-ai-lab/sim-plugin-comsol/comsol"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-plugin-comsol/comsol/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-plugin-comsol/comsol"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-plugin-comsol/comsol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00134 | $0.06863 |
| Opus 5.5 | $0.00054 | $0.02745 |
| Sonnet 5.5 | $0.00027 | $0.01373 |
| Haiku 4.5 | $0.00013 | $0.00686 |
Grade A, and why
comsol-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 1mo 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.
This is a copy
100% identical to comsol-sim — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 589 lines — stays where its author put it; the contents beside it link to each section on GitHub.
comsol-sim
This file is the COMSOL Multiphysics agent workflow index. Its job is to
help an agent choose and execute the most reliable real COMSOL control path for
the task: saved .mph inspection, local COMSOL documentation, direct COMSOL
executables, a server-backed Java API session, or the sim COMSOL runtime when
that adds useful structure.
This skill is self-contained for COMSOL work. Do not require a separate skill checkout or an external sim-cli skill. Use this file for COMSOL workflow routing, and load the plugin-bundled references below only when the task needs them.
COMSOL-specific layered content
Choose the control path from the task and the current COMSOL state. Identify
whether you have a saved .mph, a standalone Desktop, an mphclient connected
to comsolmphserver, an external comsolmphserver, or no running session.
Then pick the smallest path that can produce real evidence.
| Path | Use it for | Evidence to collect |
|---|---|---|
saved .mph inspection |
Offline summaries, archive diffs, parameters, physics tags, mesh/solution metadata, and artifact review without starting COMSOL. | inspect_mph(path), MphArchive, or mph_diff output. |
| local COMSOL docs | Unknown physics feature names, module capability, property names, examples, and API terms before writing code. | sim-comsol-doc search / retrieve hits from the installed COMSOL help tree. |
direct comsolbatch -inputfile |
Running a saved model headlessly, stripping solutions with -norun, regression/CI/fan-out over .mph files, and one-shot saved-model output artifacts. |
output .mph, -batchlog, shell exit status, and extracted KPIs/artifacts. |
comsolcompile + comsolbatch |
Settled Java recipes that build, solve, and extract KPIs in a fresh COMSOL process. | compiled class, batch log/stdout KPI lines, output .mph or exported data. |
comsolmphserver / Java API |
Stateful model exploration, live property/tag probing, incremental mutation, debugging, and API work where the agent needs to ask the live model questions. | model tags/properties, run/build results, saved checkpoints, and explicit model identity. |
| sim runtime / shared Desktop | The same server-backed Java API work when the plugin's structured inspect/exec/checkpoint tools or managed visible Model Builder collaboration are useful. |
session.health, comsol.model.identity, last.result, live binding checks, checkpoints. |
What ships with it
25 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/reference/java_api_patterns.md 6.2 KB
- base/reference/java_batch_patterns.md 9.2 KB
- base/reference/mph_file_format.md 5.9 KB
- base/reference/offline_postprocessing_exports.md 6.6 KB
- base/reference/runtime_introspection.md 4.5 KB
- base/workflows/block_with_hole/00_create_geometry.py 627 B runs code
- base/workflows/block_with_hole/01_assign_material.py 523 B runs code
- base/workflows/block_with_hole/02_setup_physics.py 906 B runs code
- base/workflows/block_with_hole/03_generate_mesh.py 201 B runs code
- base/workflows/block_with_hole/04_solve.py 277 B runs code
- base/workflows/block_with_hole/05_plot_temperature.py 340 B runs code
- base/workflows/debug_failed_exec.md 3.9 KB
- base/workflows/model_review_loop.md 2.8 KB
- doc-search/.gitignore 63 B
- doc-search/pyproject.toml 493 B
- doc-search/README.md 1.6 KB
- doc-search/src/sim_comsol_doc/__init__.py 97 B runs code
- doc-search/src/sim_comsol_doc/cli.py 3.7 KB runs code
- doc-search/src/sim_comsol_doc/discover.py 9.0 KB runs code
- doc-search/src/sim_comsol_doc/searcher.py 3.2 KB runs code
- doc-search/uv.lock 33 KB
- solver/6.0/notes.md 465 B
- solver/6.1/notes.md 455 B
- solver/6.2/notes.md 455 B
- solver/6.4/notes.md 564 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.
- 1mo ago First seen · 589 lines · 134 tokens per session scan A 0c979e297880
comsol-sim is a skill published in the GitHub repository svd-ai-lab/sim-plugin-comsol (73 stars, last pushed yesterday), licensed Apache-2.0. It adds 134 tokens to every session and 6,863 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to comsol-sim, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
comsol-sim
Use when the user asks Codex, Claude Code, ChatGPT-style coding agents, or another AI agent to build, inspect, run, debug, or revise COMSOL Multiphysics / COMSOL Desktop models. Choose the simplest real COMSOL control path for the task: saved .mph inspection, local COMSOL documentation, direct COMSOL executables…
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. Choose the simplest real Abaqus control path first: existing artifacts, direct vendor launchers/batch commands, Abaqus/CAE noGUI, or sim-cli when standardized execution, diagnostics…
hfss
Work with Ansys HFSS 3D through PyAEDT, AEDT, sim-plugin-hfss, or solver-native workflows. Use when the user asks an agent to inspect, build, edit, run, monitor, export, or debug HFSS 3D models.
fluent-sim
Use when working with Ansys Fluent through live sim sessions, direct PyFluent scripts, or file-side artifact review.
mechanical-sim
Use when driving Ansys Mechanical via PyMechanical (ansys-mechanical-core) through the sim runtime, or reading solved .rst files with DPF on the agent side. Covers boundary conditions, loads, solver execution, and result extraction. This is the physics-layer counterpart to workbench-sim (which orchestrates cells 1-3)…
flotherm-sim
Run, inspect, or troubleshoot Simcenter Flotherm thermal cases using the smallest verified local control path. Use for Flotherm installation checks, existing-project re-solves, .pack import, FloSCRIPT playback, model creation or modification, solver monitoring, and result extraction. Discover native and sim-cli…