What is sim-cli CLAUDE.md?

Project instructions for sim-cli, a tool that reads engineering simulation files and turns them into structured text for an agent. It can also find local solver installations, check scripts and keep a solver session open across steps.

Understanding the repository, scanning simulation files, discovering solver drivers, validating scripts and managing the project's tests and commands.

They explain which parts work without a solver installation and which require extra solver plugins. This helps an agent choose the right command and avoid assuming unavailable runtime features.

How svd-ai-lab/sim-cli configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to svd-ai-lab/sim-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/svd-ai-lab/sim-cli/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/svd-ai-lab/sim-cli

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/svd-ai-lab/sim-cli/claude-md/github.svg)](https://agentmods.dev/instructions/svd-ai-lab/sim-cli/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/svd-ai-lab/sim-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/svd-ai-lab/sim-cli/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/svd-ai-lab/sim-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/svd-ai-lab/sim-cli/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 4,476 This file is loaded in full into every session.

When invoked 4,476 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5.1	$0.04476	$0.04476
Opus 5.5	$0.01790	$0.01790
Sonnet 5.5	$0.00895	$0.00895
Haiku 4.5	$0.00448	$0.00448

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

Security

Grade A, and why

sim-cli CLAUDE.md 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 10d 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.

CLAUDE.md · 239 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

sim reads existing CAE files and turns them into structured text an agent can use, detects local solver installs, validates scripts, and can hold a live solver session open across steps. The pyproject.toml description — "Agent-native simulation asset parsing and CAD/CAE runtime" — states the priority correctly: parsing first, runtime second.

Know which tier you are working in, because their dependencies differ:

Asset parsing (sim scan) — pure core, no plugin, no solver, no license. Backed by the simparse native extension, a hard dependency of sim-cli-core. This is the most-used capability in practice: agents can already drive solver GUIs directly, so the highest-value thing sim does today is recover engineering context from historical case files (a preprocessing step, closer to a document-to-structured-text converter than to a solver driver).
Solver discovery and script validation (sim check, sim lint) — require the solver's plugin. With no plugins installed, check --all reports "scanned 0 drivers" and lint errors with No registered driver claims ....
Execution — requires a plugin, and comes in two modes:
- One-shot (sim run script --solver=X): subprocess execution, result stored as a numbered run, sim logs to browse.
- Persistent session (sim connect/exec/inspect/disconnect): a long-lived HTTP server holds a live solver session; agents send code snippets and inspect state without restarting the solver. sim connect auto-starts a local server when none is reachable (session.py:_auto_start_server), so sim serve is only needed explicitly for remote hosts — and sim stop is the counterpart that reaps that background process.

This tiering is load-bearing for docs and error messages: never imply sim scan needs a plugin, and never imply sim check works without one.

Read the full file on GitHub · 239 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.

10d ago Changed · +35 tokens per session 1d400443f04e
18d ago Changed · +18 tokens per session 64aad6838408
2mo ago First seen · 239 lines · 4,423 tokens per session scan A f265452b8fbb

Subscribe to this mod's changes

sim-cli CLAUDE.md is an instructions file published in the GitHub repository svd-ai-lab/sim-cli (247 stars, last pushed 10d ago), licensed Apache-2.0. It adds 4,476 tokens to every session, about $0.0179 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-08-30.

abaqus agent-skills ai-agents cae cfd physics-simulation

sim-cli CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sim-cli CLAUDE.mdsvd-ai-lab/sim-cli	Instructions file	247	10d ago	Apache-2.0	A	4,476	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

sim-cli: Instructions file for Claude Code