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 halsyourpal422/Battenmark --skill enclosuregit clone --depth 1 https://github.com/halsyourpal422/BattenmarkWrote 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/halsyourpal422/battenmark/enclosure)<a href="https://agentmods.dev/skills/halsyourpal422/battenmark/enclosure"><img src="https://agentmods.dev/badge/skills/halsyourpal422/battenmark/enclosure.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.00000 | $0.00683 |
| Opus 5 | $0.00000 | $0.00342 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
enclosure 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 today.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
3D-Printable Enclosure
Purpose
Design a mechanically credible, FDM-friendly enclosure around measured component dimensions, with clearances, mounting features, connector openings, and verification before export.
Use when
- Real component outer dimensions, connector locations, and mounting points are known or obtainable.
- Part will be printed on a consumer FDM printer.
Do not use when
- Component dimensions are unknown (do not invent numbers).
- Pure mechanical assembly of existing parts (use
assembly).
Preconditions
- REQUIRED: Measured component dimensions; explicit clearance assumptions; units mm.
- RECOMMENDED:
inspect_backend_capabilitiesif unsure about boolean/hole/export.
Planning rules
- Collect measurements first; label unknowns.
- Define parameters for sizes, wall, clearances before solids.
- Derive the main internal cavity from measured component dimensions + clearances; keep it parametric.
- The main internal cavity is independent from every connector opening; create and verify it first.
- Preserve mounting features and connector openings.
- Never invent dimensions.
Recommended operation sequence
- REQUIRED —
project_create/project_open; capture measurements as parameters. - REQUIRED — Create the outer body with
create_box(expression-driven). - REQUIRED — Create and verify the main internal cavity: derive its size from component clearances and intended wall/floor thickness; create a distinct cavity tool with
create_box; subtract it from the outer body withbooleanoperationsubtractso the top is open and the intended walls and floor remain. - REQUIRED — Create connector openings as separate downstream features, for example with
create_sketch→add_rectangle→pocketon the appropriate wall. A connector pocket is not the main cavity. - RECOMMENDED — lid, ports, standoffs, light fillets.
- REQUIRED —
validate→render_preview→rebuild→ export.
What ships with it
1 file 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.
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.
- today Changed · +15 lines 3bc622dc1aef
- 6d ago First seen · 48 lines · 0 tokens per session scan A 22a5801c5ea5
enclosure is a skill published in the GitHub repository halsyourpal422/Battenmark (0 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 683 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-31.
Other skills, from other repositories
freecad
Use when doing parametric 3D CAD modeling, BIM/architectural design, FEM simulation, CAM toolpath generation, or robot simulation with Python scripting. FreeCAD: the leading open-source parametric 3D CAD with Sketcher, Part, PartDesign, Arch, CAM, and FEM workbenches.
enclosure
Generate a parametric electronics enclosure with a base and lid.
gear
Create an involute spur gear using FreeCAD's Part module.
fastener-hole
Create standard fastener holes: clearance, counterbore, or countersink.
thread-insert
Create properly sized holes for heat-set threaded inserts (common in 3D printed parts).
kompas-mcp-operator
Operate KOMPAS-3D MCP for 2D drawings, 3D parts, CAD-as-Code scripts, screenshots, exports, runtime memory, remote/local recovery, and Graph Brain diagnostics. Use when Codex needs to create, edit, inspect, validate, or debug geometry through mcpkompas3d, especially for sketch-feature chains, reusable scenarios…