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 ladla90077-web/solidworks-mcp --skill analyze-simulation-resultsgit clone --depth 1 https://github.com/ladla90077-web/solidworks-mcpWrote 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/ladla90077-web/solidworks-mcp/analyze-simulation-results)<a href="https://agentmods.dev/skills/ladla90077-web/solidworks-mcp/analyze-simulation-results"><img src="https://agentmods.dev/badge/skills/ladla90077-web/solidworks-mcp/analyze-simulation-results/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/ladla90077-web/solidworks-mcp/analyze-simulation-results"><img src="https://agentmods.dev/badge/skills/ladla90077-web/solidworks-mcp/analyze-simulation-results.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.00014 | $0.01865 |
| Opus 5 | $0.00007 | $0.00932 |
| Sonnet 5 | $0.00003 | $0.00373 |
| Haiku 4.5 | $0.00001 | $0.00186 |
Grade A, and why
Analyze Simulation Results 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 11d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Simulation Results
What You're Actually Doing
You're helping an engineer answer a question. Every simulation exists to answer something: "Will this break?" "Is cooling adequate?" "Does this meet the spec?" Your job is to help them get to that answer with confidence.
This is not about producing a document. The report is a byproduct - a record of the reasoning that led to a conclusion. If you focus on filling out report sections, you'll produce something thorough but useless. If you focus on answering the engineer's actual question, the report writes itself.
The goal shifts based on context:
- Sometimes it's a quick sanity check: "Does this look reasonable?"
- Sometimes it's decision support: "Pass or fail against these requirements?"
- Sometimes it's investigation: "Why is this region showing high stress?"
- Sometimes it's documentation: "Create a record for stakeholders"
Read the situation. A 50-page report for a sanity check is a failure. A one-liner for a certification analysis is also a failure.
When to Check In (And Why)
Check-ins exist for one reason: when you need user input to proceed correctly.
Don't check in to show progress. Don't check in because you finished a "phase." Check in when your next action depends on information or judgment only the user can provide.
There are three natural decision points:
1. After Understanding the Setup
Before you do any analysis, make sure you understand:
- What's being analyzed and under what conditions
- What question the engineer is trying to answer
- What "success" looks like (requirements, allowables, or just "reasonable")
Why this matters: If you misunderstand the goal, everything downstream is wasted work. Five minutes of alignment here saves hours of rework.
What to confirm:
"It looks like you're evaluating [geometry] under [loading] to determine [question]. Is that right? And are there specific requirements I should compare against?"
If the setup is obvious from context or they've already told you, don't ask again.
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.
- 11d ago First seen · 195 lines · 14 tokens per session scan A 25e65de5c229
Analyze Simulation Results is a skill published in the GitHub repository ladla90077-web/solidworks-mcp (3 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 1,865 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…