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 spaceclaimgit 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/spaceclaim)<a href="https://agentmods.dev/skills/svd-ai-lab/sim-cli/spaceclaim"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/spaceclaim/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/spaceclaim"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/spaceclaim.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.00078 | $0.01091 |
| Opus 5.5 | $0.00031 | $0.00436 |
| Sonnet 5.5 | $0.00016 | $0.00218 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
spaceclaim 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpaceClaim Skill
Use this skill for Ansys SpaceClaim CAD preparation and geometry automation. SpaceClaim is usually a desktop geometry/preprocessing tool, not the solver itself. Prefer the narrowest path that gives real evidence: file inspection for simple inventory, SpaceClaim scripts for repeatable geometry commands, GUI operation for semantic face/body choices, and solver-specific tools after the geometry is exported.
Working Approach
- Probe availability before launching SpaceClaim when local state is unknown.
- Run
scripts/probe_spaceclaim.ps1when working on Windows. - Acceptable alternatives:
Get-Command SpaceClaim.exe, common Ansys install-path checks, Registry checks, or a user-providedSIM_SPACECLAIM_ROOT. - Missing
sim-cli, Python, or PyFluent is not evidence that SpaceClaim is missing; SpaceClaim often runs its own scripting host inside the desktop app.
- Run
- Inspect inputs before changing them.
- List CAD files and sidecars.
- For STEP, read the header/schema/unit lines and a small topology sample before opening the full model.
- Prefer writing derived files beside the original CAD instead of in-place edits.
- Choose the control path by task.
- Batch/script: imports, exports, simple body operations, repeatable named groups, repair sequences, or documented commands.
- GUI-assisted: face selections, cap selections, seed points, periodic cuts, flow-path choices, or anything requiring design intent.
- Solver handoff: meshing, boundary physics, convergence, and result validation belong in Fluent/Mechanical/COMSOL/etc. after CAD prep.
- After each meaningful change, verify the artifact rather than only the process exit. Check output file existence, format, units, body/face counts when available, and screenshots or exported geometry for visually sensitive work.
- Report uncertainty plainly. When the API cannot expose the geometry semantics needed for safe automation, produce a semi-automatic workflow or script template and identify the exact user selection still needed.
What ships with it
3 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.
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 · 123 lines · 78 tokens per session scan A c9ff700e5796
spaceclaim is a skill published in the GitHub repository svd-ai-lab/sim-cli (239 stars, last pushed yesterday), licensed Apache-2.0. It adds 78 tokens to every session and 1,091 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…