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 delancy827/solidworks-skills --skill sw-designergit clone --depth 1 https://github.com/delancy827/solidworks-skillsWrote 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/delancy827/solidworks-skills/sw-designer)<a href="https://agentmods.dev/skills/delancy827/solidworks-skills/sw-designer"><img src="https://agentmods.dev/badge/skills/delancy827/solidworks-skills/sw-designer/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/delancy827/solidworks-skills/sw-designer"><img src="https://agentmods.dev/badge/skills/delancy827/solidworks-skills/sw-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00038 | $0.00600 |
| Opus 5.5 | $0.00015 | $0.00240 |
| Sonnet 5.5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
sw-designer 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SolidWorks Designer
Use this skill for design decisions, parameterization strategy, design review, manufacturability checks, and pre-automation planning. If the task requires writing or executing SolidWorks API code, switch to solidworks-automation.
Design workflow
- Clarify intent. Identify the deliverable: part, assembly, drawing, mold, sheet-metal part, weldment, or review only.
- Collect constraints. Record dimensions, material, manufacturing process, tolerances, units, standards, and any downstream drawing or simulation requirements.
- Choose a modeling strategy. Prefer native基准面 and robust sketch profiles. Avoid sketching on inclined faces unless no orthogonal strategy can represent the geometry.
- Parameterize. Use an explicit parameter table or class. Do not bury dimensions in scattered literals.
- Validate design intent. Check feature order, body count, symmetry, wall thickness, fillets, chamfers, hole counts, and mating references.
- Hand off cleanly. Produce a dimension ledger and validation checklist before automation begins.
Design rules
- Fully define sketches when the geometry allows it.
- Prefer orthogonal基准面 and stable references over face-dependent selections.
- Use design tables or explicit parameter dictionaries for families of parts.
- Keep feature order editable: base geometry, secondary features, holes, fillets/chamfers, then appearance or metadata.
- For assemblies, count repeated instances before modeling and prefer standard interfaces or named references over fragile face picks.
- For drawings, check projection, annotation order, hole callouts, and tolerance stack before export.
- For molds or forming tools, compute process dimensions before CAD; do not treat part geometry as tool geometry.
Reference routes
Read only the reference that matches the task.
references/design-manual.md— full 17-chapter design guide. Search withrg -n "keyword" references/design-manual.md, then read the relevant section rather than the entire manual.../solidworks-automation/references/drawing-to-3d-lessons.md— drawing interpretation and geometry validation.../solidworks-automation/references/materials-forming-mold-lessons.md— forming and mold process checks.../solidworks-automation/references/assembly-debugging-lessons.md— assembly intent and repeated-instance rules.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -739 lines · -31 tokens per session e3e08c00dd63
- 2mo ago First seen · 784 lines · 69 tokens per session scan A bea7de1a9df3
sw-designer is a skill published in the GitHub repository delancy827/solidworks-skills (153 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 600 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.
sw-designer compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sw-designerdelancy827/solidworks-skills | Skill | 153 | 1mo ago | MIT | A | 38 | Claude Code, Codex |
| webgl-holographic-foilnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 41 | Claude Code, Codex |
| html-ppt-hermes-cyber-terminalnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 53 | Claude Code, Codex |
| html-ppt-taste-brutalistnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 78 | Claude Code, Codex |
| visual-ralphYeachan-Heo/oh-my-codex | Skill | 34k | 3d ago | MIT | A | 52 | Codex |
| glance-canonical-layoutsandroid/skills | Skill | 10k | yesterday | Apache-2.0 | A | 56 | Claude Code |
| accessibilitymicrosoft/hve-core | Skill | 1.6k | yesterday | MIT | A | 47 | Claude Code |