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 agentmods add skills/autonomous-ai/autonomous-workshop/electromechanical-integrationnpx skills add autonomous-ai/autonomous-workshop --skill electromechanical-integrationgit clone --depth 1 https://github.com/autonomous-ai/autonomous-workshopWrote 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/autonomous-ai/autonomous-workshop/electromechanical-integration)<a href="https://agentmods.dev/skills/autonomous-ai/autonomous-workshop/electromechanical-integration"><img src="https://agentmods.dev/badge/skills/autonomous-ai/autonomous-workshop/electromechanical-integration.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.00092 | $0.01932 |
| Opus 5 | $0.00046 | $0.00966 |
| Sonnet 5 | $0.00018 | $0.00386 |
| Haiku 4.5 | $0.00009 | $0.00193 |
Grade A, and why
electromechanical-integration 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electromechanical integration
A mounted electrical part is not a powered product. Trace every functional load from its source and back, select compatible hardware from authoritative evidence, and reserve real CAD space for every carried component and wire route.
Boundary
- Use GitHub open-hardware projects to learn integration patterns: battery and controller placement, connectors, hatches, wire channels, strain relief, service access, light pipes and diffusers, and assembly order.
- Never use a GitHub project's dimensions, electrical ratings or photometric ratings as authority for the user's hardware. Use manufacturer datasheets, manufacturer product pages, or applicable standards for those facts.
- Use
$step-partsfirst for bought component geometry and$cadto derive and verify seats from the component STEP. A GitHub analogy or public CAD library does not replace either one. - Do not redesign the requested exterior around an analogous repository. Fit the powered system inside the approved product form.
- A visible coloured lens is not proof of a functional light or of an exact part number. Confirm the requested function; preserve uncertainty when only the image is evidence.
Two-phase workflow
This skill is invoked before CAD layout is fixed, but its final gates consume CAD artifacts. Keep those moments explicit:
- Phase A — research/spec, before geometry: complete steps 1–4, choose the
physical integration strategy in step 5, and write the evidence and decisions
into build-spec sections 6c, 6e, 6f and 8a. Mount labels, project-local STEP
files and motion conditions may only be planned at this point. Do not claim
that
check_power,check_mountorcheck_motionran. Phase A owns the electrical, actuator and lighting selection: start with a measurable contract, research and compare, then write the selected topology, exact devices and rejected alternatives into build-spec section 6g. Do not arrive with an agent-guessed topology or MPN already locked. - Phase B — powered CAD handoff: after
$cadhas materialized the selected component STEP/envelope files, assembly labels, seats, routes and motion conditions, write the three manifests and run their gates. A pre-CAD research packet is not a substitute for this phase.
What ships with it
5 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.
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 First seen · 148 lines · 92 tokens per session scan A a2216bd9b8b7
electromechanical-integration is a skill published in the GitHub repository autonomous-ai/autonomous-workshop (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 92 tokens to every session and 1,932 once invoked, about $0.0005 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
bump-dependency
Bumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
pennylane
Hardware-agnostic quantum ML framework with automatic differentiation. Use when training quantum circuits via gradients, building hybrid quantum-classical models, or needing device portability across IBM/Google/Rigetti/IonQ. Best for variational algorithms (VQE, QAOA), quantum neural networks, and integration with…
mine
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.