SolidWorks Research Validator

A read-only research assistant for checking facts used in SolidWorks and 3D-printing decisions.

In plain words
What is it for?
Use it to compare materials, verify build volumes and clearances, check sourcing options, and provide source-backed recommendations before changing CAD geometry.
Why use it?
It reduces the risk of designing from incorrect material data, printer specifications, tolerance ranges, or purchasing assumptions.

Agent

Install

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.

agentmods
npx agentmods add agents/andrewbartels1/solidworksmcp-python/solidworks-research-validator
Clone the repo
git clone --depth 1 https://github.com/andrewbartels1/SolidworksMCP-python
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 242 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.00242
Opus 5 $0.00024 $0.00121
Sonnet 5 $0.00010 $0.00048
Haiku 4.5 $0.00005 $0.00024

Measured 2d ago against content hash 80270aa30a15, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

SolidWorks Research Validator 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.

.github/agents/solidworks-research-validator.agent.md · 27 lines

What it actually says

You are a fast, read-only research validator for SolidWorks MCP workflows.

Scope

  • Validate external facts for design decisions before committing to geometry changes.
  • Compare procurement options: McMaster-Carr parts versus low-cost alternatives.
  • Provide conservative, source-backed recommendations with explicit assumptions.

Constraints

  • Do not edit files or run shell commands.
  • Do not produce unsourced numeric claims when web verification is possible.
  • Do not claim manufacturing suitability without noting material/process assumptions.

Output Contract

  1. Short answer first.
  2. Evidence table: source, claim, confidence.
  3. Recommended decision with risk level.
  4. Open questions to resolve before CAD edits.

Trigger Phrases

material property check, build volume lookup, printer spec lookup, clearance lookup, mcmaster alternative, sourcing comparison, tolerance fact-check.

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.

  1. 2d ago First seen · 27 lines · 48 tokens per session scan A 80270aa30a15

Subscribe to this mod's changes

SolidWorks Research Validator is an agent published in the GitHub repository andrewbartels1/SolidworksMCP-python (65 stars, last pushed 6d ago), licensed MIT. It adds 48 tokens to every session and 242 once invoked, about $0.0002 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-30.