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 ppak10/RocketSmith --skill design-for-additive-manufacturinggit clone --depth 1 https://github.com/ppak10/RocketSmithWrote 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/ppak10/rocketsmith/design-for-additive-manufacturing)<a href="https://agentmods.dev/skills/ppak10/rocketsmith/design-for-additive-manufacturing"><img src="https://agentmods.dev/badge/skills/ppak10/rocketsmith/design-for-additive-manufacturing/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/ppak10/rocketsmith/design-for-additive-manufacturing"><img src="https://agentmods.dev/badge/skills/ppak10/rocketsmith/design-for-additive-manufacturing.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.00057 | $0.03987 |
| Opus 5 | $0.00028 | $0.01994 |
| Sonnet 5 | $0.00011 | $0.00797 |
| Haiku 4.5 | $0.00006 | $0.00399 |
Grade A, and why
design-for-additive-manufacturing 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 11d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design for Additive Manufacturing (DFAM)
Overview
OpenRocket describes a rocket as a logical design — a tree of abstract components (nose cone, body tubes, inner tubes, couplers, fin sets, centering rings) that captures aerodynamic and mass properties. That description is manufacturing-agnostic.
The physical parts list — what actually gets produced and assembled — is a function of the chosen manufacturing method applied to that logical design. This skill handles the additive manufacturing case: converting OpenRocket components into a printable component tree that the generate-structures skill and cadsmith subagent use as their authoritative source.
Core principle: OpenRocket components don't map 1:1 to printed parts. A centering ring in OR becomes "localised wall thickening" in AM. A tube coupler in OR becomes "integral shoulder on the forward section" in AM. A fin set in OR becomes "fused geometry on the lower airframe" in AM. The translation is the whole point of this skill.
When to Use
- The CAD phase is starting and the chosen manufacturing method is additive (FDM or SLA)
- A
component_tree.jsonis missing or stale for the current.orkfile - The user changed the design and the existing manifest needs to be regenerated
- A user explicitly asks "what parts do I actually print for this rocket?"
Inputs
- The component tree from
openrocket_component(action="read", rocket_file_path=<path>, project_dir=<project_dir>)— authoritative mm-scaled geometry and the derived motor mount / body tube ID - The default policy (passed by the orchestrator):
"additive"means print everything that can be printed and fuse aggressively;"hybrid"means print the nose cone and fin can but purchase body tubes and motor mount;"traditional"falls back to a separate skill not yet implemented - Optional user overrides on specific fusion decisions
Output
A single JSON file written to <project_dir>/gui/component_tree.json by the manufacturing_annotate_tree MCP tool. The schema is enforced by Pydantic models at tool-call time, so malformed manifests are rejected before they reach disk. This file is the authoritative handoff to generate-structures and cadsmith — they consume it and produce STEP files from it. The mass-calibration skill also reads it to map filament_used_g back to OR components via component_to_part_map.
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.
- 11d ago First seen · 319 lines · 57 tokens per session scan A b452d55bce28
design-for-additive-manufacturing is a skill published in the GitHub repository ppak10/RocketSmith (21 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 3,987 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-30.
Other skills, from other repositories
add-interfaces
Enrich an existing PartCAD part with connection interfaces and ports (mating metadata) so it can be mated to other parts automatically. Use for /pc:add-interfaces or when the user asks to add interfaces, ports, connectors, or mating information to a part, or to make parts snap/connect/assemble together.
gen-assembly
Generate a PartCAD assembly (an ASSY that composes parts with placement and/or mates) from a description, generating or reusing the component parts and validating the result with the PartCAD CLI. Use for /pc:gen-assembly or when the user asks to generate or create an assembly, mechanism, or multi-part product.
render
Render a PartCAD object or a CAD file to a 2D image - PNG, JPEG, SVG or DXF - from one or many viewing angles (front, back, left, right, top, bottom, iso, or an arbitrary direction), with pc render for an object a package declares or pc adhoc render for a file that belongs to no package. Use for /pc:render or when the…
gen-part
Generate a PartCAD part from a natural-language description (and optional reference images/requirements) by authoring a CAD script and validating it with the PartCAD CLI. Use for /pc:gen-part or when the user asks to generate, create, or model a single mechanical part.
gen-sketch
Generate a PartCAD 2D sketch from a natural-language description by authoring the sketch (build123d / cadquery / dxf / svg / basic) and validating it with the PartCAD CLI. Use for /pc:gen-sketch or when the user asks to generate, create, or draw a 2D sketch, profile, outline, or blueprint.
cad-viewer
Start CAD Viewer and return review links for CAD and robot-description files. Use when visually reviewing .step, .stp, .glb, .stl, .3mf, .dxf, .urdf, .srdf, or .sdf files, especially when handed off from CAD, URDF, SRDF, or SDF generation skills.