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 ladla90077-web/solidworks-mcp --skill drawing-plangit clone --depth 1 https://github.com/ladla90077-web/solidworks-mcpWrote 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/ladla90077-web/solidworks-mcp/drawing-plan)<a href="https://agentmods.dev/skills/ladla90077-web/solidworks-mcp/drawing-plan"><img src="https://agentmods.dev/badge/skills/ladla90077-web/solidworks-mcp/drawing-plan/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/ladla90077-web/solidworks-mcp/drawing-plan"><img src="https://agentmods.dev/badge/skills/ladla90077-web/solidworks-mcp/drawing-plan.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.00055 | $0.01133 |
| Opus 5 | $0.00028 | $0.00566 |
| Sonnet 5 | $0.00011 | $0.00227 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
Drawing Plan 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 12d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Drawing
Decide how to draw the part before drawing it. The output is a short plan the user approves or adjusts — not a finished drawing. Plan well and execution is mechanical; plan badly and you redo views and dimensions.
The standards in brackets are the authority; when nothing says which applies, default to the company standard, then ASME for inch / ISO for metric.
How to plan
- Understand the part: model type, bounding box, features, units, symmetry, internal geometry, key dimensions.
- Take screenshots of the part from multiple angles to understand the part
- Decide the manufacturing method first — it drives features, symmetry, and datums.
- Work through each decision below.
- Propose the plan with a one-line because for every choice, so the user can accept or override on judgment. Keep it short enough to approve at a glance.
- Stop and confirm before executing. Planning is the place to disagree; once drawing starts, changes are expensive.
The plan
Manufacturing method (decide first)
- How the part is made: turned, milled, cast, sheet metal, etc. — read it from the feature signature (a revolve + chamfer reads as turned).
- This sets the datum scheme: a turned part is datumed on its first turned feature; a milled part on its functional faces.
Primary view (ASME Y14.3 / ISO 128-3)
- Pick the most informative profile from the bounding box — don't assume the front view. Profiles: front = X×Y, right = Z×Y, top = X×Z; choose the one that shows the most features.
- Turned → revolve axis horizontal. Sheet metal → largest flat face. General → largest, most detailed profile.
Views — scale the set to the part's complexity:
- Simple part — the minimum set that fully describes it; give each view a purpose (section to expose a pocket, top for the hole pattern, isometric for context only).
- More complex part — add a section where internal detail matters, a detail view for features too small to dimension, an auxiliary view for inclined faces.
- Complex or long part — use broken, detail, and section views so every feature can be dimensioned without overcrowding the sheet (a broken view shortens a long uniform part so it fits at a usable scale).
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.
- 12d ago First seen · 75 lines · 55 tokens per session scan A 3ada05f678ea
Drawing Plan is a skill published in the GitHub repository ladla90077-web/solidworks-mcp (3 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 1,133 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…