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/prompt-driven-designgit 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.00000 | $0.03406 |
| Opus 5 | $0.00000 | $0.01703 |
| Sonnet 5 | $0.00000 | $0.00681 |
| Haiku 4.5 | $0.00000 | $0.00341 |
Grade A, and why
prompt-driven-design 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt-Driven Design with SolidWorks MCP
You know SolidWorks. This guide shows you how to describe what you want to build in plain language, let an LLM translate that into the right tool calls, and have SolidWorks build it — without clicking through menus.
The examples below use real SolidWorks sample parts as targets. Because the finished .SLDPRT files already exist, you can open them and check the feature tree to confirm whether your prompts produced the right result. That makes them ideal for learning the workflow before applying it to your own designs.
What You Need
- SolidWorks installed and open
- MCP server running (
.\dev-commands.ps1 dev-installthen.\dev-commands.ps1 dev-runif needed) - Claude Code (this tool) or VS Code with Copilot Chat
- Python environment activated:
.\.venv\Scripts\python.exe
The Core Workflow
Every design session follows the same loop:
flowchart LR
D(["1 - Describe<br/>What to build<br/>+ dimensions"])
P(["2 - Plan<br/>LLM proposes<br/>MCP call sequence"])
R(["3 - Review<br/>You approve<br/>the plan"])
E(["4 - Execute<br/>Claude Code runs<br/>MCP tools"])
C(["5 - Check<br/>Visual or<br/>feature-tree"])
I(["6 - Iterate<br/>Refine dimensions,<br/>add features"])
D --> P --> R --> E --> C --> I
I -->|new idea or fix| D
style R fill:#f0f4ff,stroke:#4a6cf7
style C fill:#f0f4ff,stroke:#4a6cf7
Steps 3 (Review) and 5 (Check) are yours. The LLM handles 2 and 4.
Step 1 — Describe What You're Building
Be specific about shape and size. Adjectives like "wide" or "thin" are ambiguous. Geometry and dimensions are not.
Good description
I want to create a paper airplane shape.
It should be a flat delta-wing profile — like looking down at a paper airplane from above.
The nose points right at (80, 0), the two wing tips are at (0, 60) and (0, -60),
and everything connects back to the origin.
Extrude it 0.5 mm — just enough thickness to represent folded paper.
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 · 378 lines · 0 tokens per session scan A 67af58e81a1a
prompt-driven-design is an agent published in the GitHub repository andrewbartels1/SolidworksMCP-python (65 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,406 tokens. 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
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
product-lead
Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
i18n
你是一个精通 Vue3 国际化架构的前端专家(专注于 Vue3 + TypeScript + Composition API)。同时,你也是一位专业的 UI/UX 翻译专家,擅长将中文界面语言翻译为地道、简洁的英文。.
chat-agent-spec
应实现于: /src/everlingo/agents/agent.py ,主要实现在 class MainAgent 。.
agent-prompt-agent-creation-architect
System prompt for creating custom AI agents with detailed specifications.