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 luckiday/vibe-hardware --skill vibe-industrial-designgit clone --depth 1 https://github.com/luckiday/vibe-hardwareWrote 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/luckiday/vibe-hardware/vibe-industrial-design)<a href="https://agentmods.dev/skills/luckiday/vibe-hardware/vibe-industrial-design"><img src="https://agentmods.dev/badge/skills/luckiday/vibe-hardware/vibe-industrial-design/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/luckiday/vibe-hardware/vibe-industrial-design"><img src="https://agentmods.dev/badge/skills/luckiday/vibe-hardware/vibe-industrial-design.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.00580 | $0.04422 |
| Opus 5 | $0.00290 | $0.02211 |
| Sonnet 5 | $0.00116 | $0.00884 |
| Haiku 4.5 | $0.00058 | $0.00442 |
Grade A, and why
vibe-industrial-design 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe industrial design (brief + AI look image → parametric appearance → renders → report)
You own what it looks like: proportions, split lines, panel inset, control
placement, CMF. vibe-cad owns how it holds together. The two meet on a few
shared numbers (outer W×H×D, corner radii, apertures) that you decide here and
hand over.
The method has three sources of truth and one loop:
params.js— every dimension, once, with a provenance tag. Nobody types a number anywhere else.design-report.md— the written authority (ID · CMF · manufacturability · open questions · version log). The.docxis a generated snapshot of it.studio.blend— the hand-tuned lighting/materials, extracted so they outlive the model.
constraints ─► AI look image(s) ─► MEASURE ─► params.js ─► three.js scene ─► contact sheet ─► GLB ─► Blender shots ─► report vN
+ brief (Midjourney/ px/mm, [tag] each outline×profile 6 fixed views mm→m studio.blend md + docx
Imagen/gpt-image) ratios value + plates w/ holes raster (reused) + change log
▲ ▲ │ │
│ └───── you send the current render back ───┘ (edit = refine the form, generate = leave it) │
└──────────── owner sends a new image ("v+1: more like this") ◄─────────────────────────────────────────────┘
0. Constraints first: what already decided the form
Before the first picture, go and find the constraints that are already fixed — they are rarely all in the brief. An algorithm spec that assumed a mounting height and derived its thresholds from it; an ADR whose module needs an antenna keep-out; a human-machine contract saying which two controls must never be confusable; a board contract with a power LED the MCU cannot switch off. Extract them into the report's §0 before you have a picture to fall in love with.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/ai-image-iteration.md 4.8 KB
- references/appearance-vs-physics.md 5.7 KB
- references/blender-pipeline.md 5.5 KB
- references/design-report.md 3.7 KB
- references/reference-image-measurement.md 3.7 KB
- references/threejs-scene-gotchas.md 7.7 KB
- scripts/blender_extract_studio.py 2.3 KB runs code
- scripts/blender_render.py 4.9 KB runs code
- scripts/blender_scenelib.py 11 KB runs code
- scripts/blender_shots.py 4.1 KB runs code
- scripts/measure_ref.py 4.1 KB runs code
- scripts/serve.py 2.3 KB runs code
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 · 273 lines · 580 tokens per session scan A 1da73b826265
vibe-industrial-design is a skill published in the GitHub repository luckiday/vibe-hardware (5 stars, last pushed 20d ago), licensed MIT. It adds 580 tokens to every session and 4,422 once invoked, about $0.0029 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
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.
solidworks-vibecad
A planning guide for turning natural-language mechanical design requests into structured, parameterized SolidWorks plans that can be reviewed before execution.
FluidCAD-assembly
Building multi-part models in FluidCAD: assemblies, part files, inserting and mating parts, connectors, exposed geometry, part parameters, sub-assemblies, replicated instances, STEP parts, project units, and assembly export. Use this skill whenever the user wants an assembly, a mechanism, a hinge, a slider, several…
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…