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 pzfreo/build123d-mcp --skill b123d-editgit clone --depth 1 https://github.com/pzfreo/build123d-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/pzfreo/build123d-mcp/b123d-edit)<a href="https://agentmods.dev/skills/pzfreo/build123d-mcp/b123d-edit"><img src="https://agentmods.dev/badge/skills/pzfreo/build123d-mcp/b123d-edit/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/pzfreo/build123d-mcp/b123d-edit"><img src="https://agentmods.dev/badge/skills/pzfreo/build123d-mcp/b123d-edit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.02971 |
| Opus 5 | $0.00000 | $0.01486 |
| Sonnet 5 | $0.00000 | $0.00594 |
| Haiku 4.5 | $0.00000 | $0.00297 |
Grade A, and why
b123d-edit 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 6d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit Existing build123d Geometry (b123d-edit)
Use this skill when the task is to change an existing build123d model or script: "make this bracket 5 mm taller", "move the holes inward", "add a counterbore", "remove this rib", "make it fit this mating part", or "repair the code so the intended edit remains parametric".
The goal is not to sculpt the final B-rep. The goal is to make an explicit, reviewable code edit that preserves design intent, then prove the changed model is valid and the intended delta happened.
Step 0 - Establish the Baseline
Before editing, capture what exists.
-
Read the source script or recover the session code with
script(). -
Run the current model in the MCP session with
execute(). -
Register the edited target with
show(part, "baseline")or a meaningful name. -
Capture numeric evidence:
save_snapshot("before_edit") print(measure(part)) -
Run the MCP
validate()tool on the registered baseline. For tasks whose deliverable is an exported solid, or where downstream CAD consumers will read a STEP/STL/BREP file, also export the unchanged baseline to a safe throwaway path such as_baseline_gate.stepand read the export gate result. The throwaway baseline gate must never use the final deliverable path, such asoutput.step. For script-only work, a successful rebuild plusvalidate()is the baseline proof unless the task later requires a file export. -
If the baseline fails the relevant proof (
validate()for script-only work;validate()plus the throwaway export gate for exported-solid work), stop and switch tobuild123d://skill/repair. Until a repaired baseline passes that same proof, the only geometry-changing operations allowed are minimal baseline fixups. Do not move, cut, extend, remove, or replace the requested target feature while the baseline is still invalid. Do not combine a feature edit with geometry repair unless the requested edit is the repair. -
After the baseline passes the relevant proof, save a snapshot such as
save_snapshot("valid_baseline"). Only then begin the requested feature or parameter edit.
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.
- 6d ago Changed · +12 lines 5a0bd3a5d180
- 11d ago First seen · 289 lines · 0 tokens per session scan A 2deeb8b8f8a5
b123d-edit is a skill published in the GitHub repository pzfreo/build123d-mcp (85 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,971 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 skills, from other repositories
exasol-import-export
Exasol IMPORT and EXPORT SQL statements: syntax, file formats (CSV, FBV, Parquet), cloud storage (S3, Azure, GCS), connection objects, error handling, and ETL staging patterns.
aieng-closed-loop-copilot
MCP-first closed-loop CAD/CAE copilot skill for improving an existing solved design against explicit targets. Use when the user asks for bounded design iteration using editable CAD parameters, solver reruns, and evidence-backed comparison.
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
mlflow-traces
Use when working with MLflow traces: debugging via MCP tools, analyzing performance, logging feedback, writing custom scorers/evaluations, or cleaning up trace data.
gemini-visualize
Generates interactive HTML visualizations (concept maps, evidence networks, knowledge graphs) from Gemini analysis results. Triggers automatically after /gr:video, /gr:research, /gr:analyze.
video-explainer
Teaches Claude how to use the 15 video explainer tools to create explainer videos from research content. Activates when working with video synthesis, explainer creation, or the video-explainer MCP server.