Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/roomi-fields/electra-one-mcpnpx agentmods add skills/roomi-fields/electra-one-mcp/dev-electra-oneWrote 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/roomi-fields/electra-one-mcp/dev-electra-one)<a href="https://agentmods.dev/skills/roomi-fields/electra-one-mcp/dev-electra-one"><img src="https://agentmods.dev/badge/skills/roomi-fields/electra-one-mcp/dev-electra-one.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.00156 | $0.06239 |
| Opus 5 | $0.00078 | $0.03120 |
| Sonnet 5 | $0.00031 | $0.01248 |
| Haiku 4.5 | $0.00016 | $0.00624 |
Grade A, and why
dev-electra-one scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
FIREBASE_API_KEY=$(for js in $(curl -s https://app.electra.one/presets/ | grep -oE '/_nuxt/[a-z0-9]+\.js' | sort -u); do How it starts
The opening of the file, as written. The whole thing — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dev-electra-one
You are about to work on the Electra One MK2 MIDI controller — a programmable
device whose Lua API and firmware behave in several non-obvious ways. This
skill exists because we have lost hours, multiple times, rediscovering things
that are already documented in HOWTO.md or in this skill. Do not start
typing Lua before you've read the relevant material.
Trust the documented quirks. Most of them are silent failures: the widget renders as a default blue fader fallback, with no error in the browser console because the logger is off by default. By the time you "see" the problem, your only feedback is a bug-report-shaped silence.
Always do this first
- Read the official doc via RTFM, not via WebFetch. The
electraone-widgetsproject workspace has a local mirror ofdocs.electra.oneat.electra-docs/md/(79 pages, including the entire Lua crash course) indexed by RTFM. Usemcp__rtfm__rtfm_search "<query>"to find relevant sections,mcp__rtfm__rtfm_expandto read them. The official docs ARE the source of truth — most behaviours we previously thought were "undocumented gotchas" turn out to be explicitly described once you grep the right page. - Open the project's
HOWTO.mdsections 1 and 2 for the workflow we use (custom-paint pattern, Firestore PATCH push). - Check
MEMORY.mdentryproject_e1_device_gotchasfor any firmware-specific quirks learned that aren't in the docs. - Only after doing the above, write code.
If a piece of behaviour isn't covered in those documents and you have to
figure it out from scratch, add it back to HOWTO.md before
considering the work done. Don't invent gotchas from intuition — grep
the local doc mirror first.
The Lua API on device (firmware 4.1.4, verified 2026-05-25)
These are the things the official docs at docs.electra.one/developers/luaext.html
either don't say or don't make obvious. Treat every one of these as a hard
constraint, not a recommendation — most cause silent fallback to the default
blue fader rendering.
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 · 443 lines · 156 tokens per session scan A 80b0afe87dcb
dev-electra-one is a skill published in the GitHub repository roomi-fields/electra-one-mcp (5 stars, last pushed 2mo ago), licensed MIT. It adds 156 tokens to every session and 6,239 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
unifi-protect
How to manage UniFi Protect cameras and NVR — view cameras, smart detections, Find Anything detection search, recordings, snapshots, lights, sensors, Known Faces, license plates, and the Alarm Manager. Use this skill when the user mentions UniFi cameras, security cameras, NVR, recordings, motion detection, person…
unifi-access
How to manage UniFi Access door control — locks, credentials, visitors, access policies, and events. Use this skill when the user mentions UniFi Access, door locks, door access, building access, NFC cards, PIN codes, visitor passes, access policies, access schedules, door readers, or any UniFi Access task.
network-health-check
Run a UniFi network health check — diagnose device status, connectivity issues, firmware updates, and system health. Use when asked to check network health, find what's down, diagnose connectivity issues, or get a network status summary.
unifi-access-support
Generate a sanitized UniFi Access support bundle, help the user review it locally, and prepare it for a bug report without posting it.
hardware-health-check
Out-of-band hardware health via Redfish BMC (read-only) — power state, component health, thermal and power readings, firmware inventory, SEL log triage. Use when determining whether a host is powered off versus unreachable, checking hardware faults, reviewing thermal or PSU state, or triaging BMC event logs.
eplan-development
Develop EPLAN Electric P8 scripts, API extensions, and remote-control applications. Use when writing C# scripts for EPLAN (actions, event handlers, ribbon), accessing the EPLAN API (parts database, projects, pages), building external apps that drive EPLAN via Remote Client, or debugging EPLAN automation issues…