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 abaqusgit 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/abaqus)<a href="https://agentmods.dev/skills/svd-ai-lab/sim-cli/abaqus"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/abaqus/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/abaqus"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/abaqus.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.00092 | $0.02668 |
| Opus 5.5 | $0.00037 | $0.01067 |
| Sonnet 5.5 | $0.00018 | $0.00534 |
| Haiku 4.5 | $0.00009 | $0.00267 |
Grade A, and why
abaqus-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.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
abaqus-sim
This file is the Abaqus index. Prefer direct local evidence first: existing
.inp/.odb/.dat/.sta/.msg artifacts, Abaqus/SIMULIA command launchers,
installed vendor docs, or user-provided paths. Use sim-cli for solver execution
and live CAE authoring when its wrapping adds useful structure.
Abaqus is a commercial finite element analysis (FEA) solver by Dassault Systemes SIMULIA. The sim plugin supports two execution styles:
- Batch execution for complete
.inpdecks or Abaqus/CAE Python files. - CAE authoring sessions for iterative model creation, inspection, debugging, job submission, and report preparation. The default backend is file-backed; the optional bridge backend keeps one noGUI CAE process alive for faster agent loops.
It supports two script formats:
- Input decks (
.inp) — keyword-driven text files defining geometry, materials, loads, BCs, and analysis steps - Abaqus/CAE Python scripts (
.py) — Python scripts using theabaqusandabaqusConstantsmodules for parametric model building
The driver runs these via subprocess (abaqus job=X input=file.inp interactive or abaqus cae noGUI=script.py). In CAE authoring sessions,
each uv run sim exec snippet runs inside Abaqus/CAE against a saved session .cae
database, then saves the database back for the next step. With
--backend bridge, snippets are sent to one long-lived noGUI CAE process over
a localhost command channel protected by a per-session token. Use bridge mode
only in trusted workspaces owned by the session user. No Abaqus Python module
is imported into the sim process.
This is not the Ansys Mechanical plugin. Do not route Abaqus .inp
decks or Abaqus/CAE Python scripts through solver=mechanical; use
solver=abaqus for Abaqus execution/authoring and solver=mechanical only
for PyMechanical / Ansys Mechanical sessions.
base/ — always relevant
| Path | What's there |
|---|---|
base/reference/input_deck_reference.md |
.inp file format: keyword syntax, node/element definitions, material, steps, BCs, output requests. |
base/reference/abaqus_scripting.md |
Abaqus/CAE Python scripting: mdb, Part, Material, Step, Load, Job objects. |
base/reference/doc_lookup.md |
How to check installed/official Abaqus docs, command help, fetched examples, and runtime API probes before guessing syntax. |
base/reference/authoring_workflow.md |
Agent workflow for iterative CAE modeling with connect, exec, inspect, and saved .cae state. |
base/reference/debug_reporting.md |
Debug loop and report checklist for .msg, .sta, .dat, ODB-derived results, assumptions, and acceptance criteria. |
base/reference/analysis_types.md |
Supported analysis types: Static, Dynamic, Heat Transfer, Coupled, etc. |
base/snippets/ |
Tested execution snippets (cantilever beam E2E). |
base/known_issues.md |
Vendor quirks and workarounds discovered during testing. |
What ships with it
10 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/known_issues.md 1.4 KB
- base/reference/abaqus_scripting.md 3.4 KB
- base/reference/analysis_types.md 2.5 KB
- base/reference/authoring_workflow.md 5.5 KB
- base/reference/debug_reporting.md 4.2 KB
- base/reference/doc_lookup.md 4.6 KB
- base/reference/input_deck_reference.md 3.2 KB
- base/snippets/01_cantilever_beam.inp 1021 B
- base/workflows/cantilever/evidence/README.md 374 B
- solver/2026/notes.md 1.2 KB
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 · 196 lines · 92 tokens per session scan A 8cc9950f05be
abaqus-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 92 tokens to every session and 2,668 once invoked, about $0.0004 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…