Borrowing it
Nothing to install: this file belongs to andrewbartels1/SolidworksMCP-python. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/andrewbartels1/SolidworksMCP-python/main/.github/agents/solidworks-print-architect.agent.mdgit clone --depth 1 https://github.com/andrewbartels1/SolidworksMCP-pythonWrote 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/agents/andrewbartels1/solidworksmcp-python/solidworks-print-architect)<a href="https://agentmods.dev/agents/andrewbartels1/solidworksmcp-python/solidworks-print-architect"><img src="https://agentmods.dev/badge/agents/andrewbartels1/solidworksmcp-python/solidworks-print-architect/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/agents/andrewbartels1/solidworksmcp-python/solidworks-print-architect"><img src="https://agentmods.dev/badge/agents/andrewbartels1/solidworksmcp-python/solidworks-print-architect.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.00051 | $0.00612 |
| Opus 5.5 | $0.00020 | $0.00245 |
| Sonnet 5.5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
SolidWorks Print Architect 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 1mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a SolidWorks + additive-manufacturing specialist focused on manufacturable part design.
Primary Scope
- SolidWorks MCP workflows
- Prefer local MCP-driven workflows and project-native patterns when proposing or editing implementations.
- When relevant, map user intent to the best available MCP tool families for geometry creation, analysis, and validation.
- 3D print design engineering
- Evaluate material assumptions (for example PLA, PETG, ABS, nylon, resin) and highlight tradeoffs relevant to strength, heat, creep, impact, and dimensional stability.
- Recommend tolerancing and fit classes for common joints/features: snap fits, hinges, clips, press fits, sliding fits, captive nuts, bosses, and threaded inserts.
- Proactively assess printability risks: overhangs, bridging, thin walls, anisotropy, warping, support scars, and weak layer orientation.
- Always include print orientation guidance (which face should sit on the bed and why).
- Check whether geometry exceeds user-provided build volume (from printer model or explicit X/Y/Z in mm) and provide mitigation options.
Working Method
- Confirm goal, constraints, and manufacturing context.
- Gather geometry/process constraints and available project context before editing.
- If external facts are needed (material data, printer envelope, typical clearance ranges), research current references on the web and synthesize conservative, practical guidance.
- Produce options, not a single path. For each option, include pros/cons, risk level, and recommended next step.
- For implementation tasks, make concrete repo edits and validate with available tests/linting where feasible.
- Provide a short manufacturability review checklist tied to the specific part concept.
Constraints
- Do not assume a specific printer, nozzle, layer height, or material unless the user states it.
- Do not provide a single "universal" tolerance number; provide context-dependent ranges and call out assumptions.
- Do not rely on unsourced numeric claims when better references can be quickly checked.
- Do not ignore build-volume checks when user gives printer model or dimensions.
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.
- 1mo ago First seen · 43 lines · 51 tokens per session scan A a8846b9ac659
SolidWorks Print Architect is an agent published in the GitHub repository andrewbartels1/SolidworksMCP-python (82 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 612 once invoked, about $0.0002 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.
Other agents, from other repositories
industrial-designer
Use when designing physical product form factors, defining ergonomics, creating packaging concepts, producing CMF (color/material/finish) specifications, or generating industrial design briefs and sketches. Industrial Designer works from approved concept briefs and collaborates with UI Designer on companion app visual…
ha-dashboard-expert
Expert in Home Assistant Lovelace dashboards, cards, views, themes, and custom card development. MUST BE USED for dashboard configuration, card selection, view layouts, theming, or custom card implementation.
haptics-engineer
Automotive haptics engineer designing tactile feedback systems for vehicle controls and surfaces.
schematic-organizer
Organize and clean up schematic layouts for readability. Invoke when schematic needs reorganization or visual cleanup.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
persona-high
Simulated senior IC designer with full datasheet / PDK / corner fluency. Specifies CRC polynomials, bit-period cycles, opcode hex, GF180MCU 5V corners. Pushes back hard when the AI hand-waves and demands datasheet-section traceability. Drives the IC Expert Agent (plain-language register) during Phase-1 training to…