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 external-solver-discoverygit 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/external-solver-discovery)<a href="https://agentmods.dev/skills/svd-ai-lab/sim-cli/external-solver-discovery"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/external-solver-discovery/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/external-solver-discovery"><img src="https://agentmods.dev/badge/skills/svd-ai-lab/sim-cli/external-solver-discovery.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.00084 | $0.01688 |
| Opus 5.5 | $0.00034 | $0.00675 |
| Sonnet 5.5 | $0.00017 | $0.00338 |
| Haiku 4.5 | $0.00008 | $0.00169 |
Grade A, and why
external-solver-discovery 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 yesterday.
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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
External Solver Discovery
Use this skill when a user needs a solver, third-party plugin, MCP server, native API, or cloud service that is not already covered by a bundled solver-specific skill.
This skill is an ad hoc discovery layer. It does not make an external solver supported, installed, licensed, authenticated, or available. It helps the agent find credible local or user-configured routes and report evidence honestly.
Required Protocol
- Name the requested capability and distinguish it from bundled solver support. For example, HFSS support is 3D EM support, not FDTD support.
- Check the current runtime before network-dependent discovery:
- attached files and workspace extensions
- project package files and scripts
- installed commands, environment variables, registry/app paths, and common application locations
- visible skills, plugins, MCP tools, connector tools, and native APIs
- user-provided licenses, paths, profiles, or account hints
- If a third-party skill, plugin, or MCP server is visible, inspect its own manifest, README, SKILL file, tool schema, or help output before using it. Prefer integrations that expose provenance, version, tool list, and logs.
- Do not install packages, enable cloud services, consume a license seat, submit jobs, or authenticate accounts without user approval.
- Probe the smallest real route first:
- version or import check
- open/list a project without solving
- dry script parse
- tiny example run
- MCP health/tool-list call
- Treat command success as transport evidence only. Engineering evidence must come from solver logs, exported data, result files, convergence, field data, S-parameters, or another domain-specific output requested by the user.
- If no credible route is available, state exactly what is missing and give the narrowest next step, such as a vendor install path, Python environment, package install, MCP server command, API key, or license check.
What ships with it
2 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.
- yesterday Changed · +1 lines 46891bcffac6
- 2d ago First seen · 145 lines · 84 tokens per session scan A f124a219fb03
external-solver-discovery is a skill published in the GitHub repository svd-ai-lab/sim-cli (239 stars, last pushed yesterday), licensed Apache-2.0. It adds 84 tokens to every session and 1,688 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…