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 skills/ed3design/ed3design-engineering-bundles/cad-api-scriptingnpx skills add Ed3Design/ed3design-engineering-bundles --skill cad-api-scriptinggit clone --depth 1 https://github.com/Ed3Design/ed3design-engineering-bundlesWrote 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/ed3design/ed3design-engineering-bundles/cad-api-scripting)<a href="https://agentmods.dev/skills/ed3design/ed3design-engineering-bundles/cad-api-scripting"><img src="https://agentmods.dev/badge/skills/ed3design/ed3design-engineering-bundles/cad-api-scripting.svg" alt="Measured on agentmods" 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 | $0.00169 | $0.01963 |
| Opus 5 | $0.00084 | $0.00981 |
| Sonnet 5 | $0.00034 | $0.00393 |
| Haiku 4.5 | $0.00017 | $0.00196 |
Grade A, and why
cad-api-scripting 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 5d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CAD API Scripting
A skill for generating, reviewing, and debugging code that drives CAD systems programmatically. Covers Python-based APIs (commercial CAD platforms), declarative languages (OpenSCAD), and similar scripting interfaces.
When to use
- User has a finished or near-finished design and wants to translate it into a reusable script
- User wants to import a parameter table into a CAD system from JSON/CSV
- User wants to generate repetitive geometry algorithmically (grids, arrays, variant families)
- User is debugging an existing CAD script
- User wants to expose a design as a configurable OpenSCAD module
When NOT to use
- User is still exploring design options →
design-first-iteration - User wants step-by-step manual CAD guidance →
cad-construction - User wants general mechanical design principles →
mechanical-design-principles - User wants firmware code or web backend code → other engineering skills
Workflow
Phase 1: Clarify the target platform
Before writing a single line, confirm:
- Which CAD platform / scripting language?
- Commercial (Fusion 360, SolidWorks, Onshape, Inventor, NX) — almost always Python or JavaScript-based
- Open-source (FreeCAD, Blender for CAD, OpenSCAD, CadQuery, Build123d)
- Declarative (OpenSCAD, JSCAD)
- Which API version / library version? APIs change. An older Fusion 360 script may not run on the current API.
- Goal of the script: one-shot generation, reusable module, parameter-import utility, test harness?
If the user is unclear, ask 1–2 targeted questions. Do not assume.
Phase 2: Sketch the code structure before writing
For non-trivial scripts, outline in plain text first:
- Setup (imports, app/document handle, parameter loading)
- Parameter definitions (from file or hardcoded)
- Helper functions (reusable geometry operations)
- Main construction sequence (sketches, features, assembly)
- Error handling and cleanup
- Save / export step
This structure sketch is the place to catch missing inputs, unclear naming, or scope creep — not the middle of a 200-line script.
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.
- 5d ago First seen · 151 lines · 169 tokens per session scan A a0dab87f4d01
cad-api-scripting is a skill published in the GitHub repository Ed3Design/ed3design-engineering-bundles (2 stars, last pushed 1mo ago), licensed MIT. It adds 169 tokens to every session and 1,963 once invoked, about $0.0008 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
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
add-cloud-flow
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.