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 print-preparationgit 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/print-preparation)<a href="https://agentmods.dev/skills/ppak10/rocketsmith/print-preparation"><img src="https://agentmods.dev/badge/skills/ppak10/rocketsmith/print-preparation.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.1 | $0.00025 | $0.01025 |
| Opus 5 | $0.00013 | $0.00513 |
| Sonnet 5 | $0.00005 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
print-preparation 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 7d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Print Preparation
Overview
Slicing converts STEP files into printer-ready gcode. Settings vary significantly by part — structural components need full infill and strong layer orientation; fairings and nose cones can use partial infill to save mass.
Core principle: Mass is the enemy of apogee. Use the minimum infill and wall count that still meets structural requirements for each part.
When to Use
- STEP files are generated and verified
- User asks to prepare parts for printing
- Choosing orientation, infill, or material for a specific part
Steps
1. Confirm STEP Files Exist
Verify all parts listed in <project_dir>/gui/component_tree.json have corresponding STEP files in <project_dir>/cadsmith/step/. If any are missing, use rocketsmith:generate-structures (Pass 1) and rocketsmith:modify-structures (Pass 2) to produce them from the manifest.
2. Choose Settings Per Part
| Part | Orientation | Infill | Perimeters | Notes |
|---|---|---|---|---|
| Body tubes (all sections) | Vertical (tube axis = Z) | 40–60% | 4–6 | Layer lines along stress axis |
| Motor mount | Vertical | 60–80% | 4–6 | High thermal load near motor |
| Centering rings | Flat (ring in XY) | 100% | 4 | Print ×2 |
| Nose cone | Tip-up or tip-down | 20–40% | 3–4 | No supports if shoulder at base |
| Lower airframe with fins | Vertical | 40–60% | 4–6 | Fins will have cross-grain layers — acceptable at model scale |
2.5. Check the Reference Collection for Print Gotchas
For parts with unusual geometry (thin walls, overhanging fin tips, large bridges), query rag_reference(action="search", collection="print_gotchas", query=f"{part_name} {distinctive_feature}", n_results=3). Fall back to the heuristic table above if no results; proceed silently on errors. Skip for simple parts that match the table cleanly.
3. Slice Each Part
prusaslicer_slice(model_file_path=<step_path>)
If out_path is omitted, gcode saves alongside the STEP file with .gcode extension.
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.
- 7d ago First seen · 89 lines · 25 tokens per session scan A 61405cb274a5
print-preparation is a skill published in the GitHub repository ppak10/RocketSmith (21 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 1,025 once invoked, about $0.0001 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.
search
Find existing PartCAD parts and assemblies in the catalog that match a natural-language query, using the PartCAD CLI (pc search), then present the matches and optionally inspect or render a chosen one. Use for /pc:search or when the user asks to search, find, look up, or discover a part or assembly.
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.