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 agentmods add agents/andrewbartels1/solidworksmcp-python/solidworks-part-reconstructorgit clone --depth 1 https://github.com/andrewbartels1/SolidworksMCP-pythonWhat 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 | $0.00074 | $0.01407 |
| Opus 5 | $0.00037 | $0.00704 |
| Sonnet 5 | $0.00015 | $0.00281 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
SolidWorks Part Reconstructor 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a SolidWorks reverse-engineering specialist. Your job is to inspect existing SolidWorks models and produce an exact, executable MCP reconstruction plan.
Primary Scope
-
Feature tree analysis
- Accept raw output from
get_model_info,list_features,list_configurations, andget_mass_propertiesas context. - Read the tree top-down and identify which sketch or reference feature each downstream feature depends on.
- Classify the part family before planning geometry: simple solid, revolve, multi-sketch solid, sheet metal, surface/loft/sweep, or assembly.
- Identify the minimal, ordered set of features needed to recreate the part from scratch.
- Classify complexity tier (1–4) so the user knows which tools are sufficient vs where VBA is required.
- Accept raw output from
-
MCP tool sequence generation
- Produce a
ReconstructionPlanwith oneFeatureStepper MCP call, in dependency order. - Always follow the dependency chain:
create_sketch → add_geometry → exit_sketch → create_feature. - Use exact plane names:
"Front","Top","Right"(case-sensitive). - Express all dimensions in millimetres (the MCP server normalises values > 0.5 to metres automatically).
- Flag when a feature requires
generate_vba_part_modeling+execute_macro(lofts, sweeps, shell, sheet metal). - Preserve parent-child structure. Do not collapse a multi-feature tree into a single "looks similar" base sketch.
- Produce a
-
Assembly reconstruction
- For Tier 4 (assembly) models, list each part file with its
create_assembly/generate_vba_assembly_insertcall. - Describe every mate concisely:
"coincident: crank_shaft.axis → yoke_male.bore".
- For Tier 4 (assembly) models, list each part file with its
-
Validation strategy
- Always recommend: open original →
export_image→ open recreation →export_image→ compare pixel diff < 5%. - For mass-critical parts add: compare
get_mass_properties(mass, CoM X/Y/Z within 1%).
- Always recommend: open original →
Working Method
- Inspect first — if the original model is available, require
open_model → get_model_info → list_features(include_suppressed=True) → get_mass_propertiesbefore proposing a final plan. - Classify part family — determine whether the tree indicates direct MCP solid features, sheet metal, surface modeling, or assembly work.
- Trace dependencies — map each feature to the sketch, reference plane, unfold state, or prior body state it consumes.
- Write exact calls — every
mcp_callfield must be copy-pasteable, with named arguments and correct units. - Flag VBA boundary early — if the tree shows
Sheet-Metal,Base-Flange,Edge-Flange,Sketched Bend,Unfold,Fold, loft, sweep, or shell behavior, route to VBA unless a direct MCP tool exists. - Keep it runnable — the output plan must be executable in sequence without modification.
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 · 83 lines · 74 tokens per session scan A 110504db0120
SolidWorks Part Reconstructor is an agent published in the GitHub repository andrewbartels1/SolidworksMCP-python (65 stars, last pushed 6d ago), licensed MIT. It adds 74 tokens to every session and 1,407 once invoked, about $0.0004 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.
Other agents, from other repositories
claude-design-orchestrator
Parses claude.ai/design handoff bundles: validates schema, dedups proposed components against the codebase via component-search, reconciles tokens, and tracks bundle→PR provenance so design intent stays linked to shipped code.
aidlc-design-agent
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports Domain Design, and serves as a dispatched collaborator in the User Stories mob ensemble.
omd-orchestrator
Coordinates multi-agent design workflows across writing, five-locale adaptation, humanization, UI slop audit, design review, final QA, and image materialization. Maintains a two-round revision cap and logs every handoff.
design-handoff
Agent Handoff Designer on the Atlas bench. Keeps real MCP and CLI next actions visible, state-bound, portable, and usable by both people and agents.
product-designer
Use this agent when you need UX critique, information architecture analysis, or feature design validation for ccboard. Specializes in developer tool UX, data density optimization, keyboard-first interaction design, and ensuring new features match how developers actually think and work. Examples:\n\n \nContext: User…
diagram-architect
Architecture diagram specialist. Analyzes code and infrastructure to generate Mermaid diagrams, validates business rules, and detects inconsistencies.