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.
git clone --depth 1 https://github.com/atopile/packagesWrote 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/rules/atopile/packages/vibe_electronics)<a href="https://agentmods.dev/rules/atopile/packages/vibe_electronics"><img src="https://agentmods.dev/badge/rules/atopile/packages/vibe_electronics/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/rules/atopile/packages/vibe_electronics"><img src="https://agentmods.dev/badge/rules/atopile/packages/vibe_electronics.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.01177 | $0.01177 |
| Opus 5.5 | $0.00471 | $0.00471 |
| Sonnet 5.5 | $0.00235 | $0.00235 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
vibe_electronics 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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How LLMs can design electronics:
#1 Rule: (repeat after me) we dont fuck around with hacky shit, we use the tools. If the tools dont work, dont freak out, you are probably using them wrong. Ask for help if you get stuck.
Top level design
- Research available packages relevant to the user requests using 'find_packages'
- Inspect promising packages using 'inspect_package'
- Propose packages to use for project and architucture to user, revise if needed
- Install needed packages using 'install_package'
- Import packages into main file
- Create instances of packages in main module
Power
- Review for each package the required voltage and current (current may not be provided, use judement if nessesary)
- Determine the power rails that need to be generated and a suitable tollerance (typically ~3-5% is acceptable)
- Determine the input power source, typically a battery, USB connector or other power connector (eg XT30) and install relevant package
- Find suitable regulators: a) if input voltage > required voltage and current is low, use an LDO package b) if input voltage > required voltage and current is high, use buck converter c) if input votlage < required voltage, use a boost converter d) if input voltage can be both less than or greater than input voltage, use buck boost (eg battery powered device that needs 3v3)
- If battery powered, add charger package
Typical power architucture example with LDO:
- USB input power
- Low current output (eg microcontroller)
from "atopile/ti-tlv75901/ti-tlv75901.ato" import TLV75901_driver from "atopile/usb-connectors/usb-connectors.ato" import USBCConn
module App:
# Rails
power_5v = new Power
power_3v3 = new Power
# Components
ldo = new TLV75901_driver
usb_connector = new USBCConn
# Connections
usb_connector.power ~ power_vbus
power_vbus ~> ldo ~> power_3v3
Communicaions
- Review packages required interfaces, typically i2c, spi or ElectricLogics
- Find suitable pins on the controller, typically a microcontroller or Linux SOC
- Connect interfaces eg micro.i2c[0] ~ sensor.i2c
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.
- 1mo ago First seen · 122 lines · 1,177 tokens per session scan A 53007741f4be
vibe_electronics is a cursor rule published in the GitHub repository atopile/packages (18 stars, last pushed 5mo ago), licensed MIT. It adds 1,177 tokens to every session, about $0.0047 per session on Opus 5.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-09-01.
Other cursor rules, from other repositories
audio-streaming
Configure and receive PCM audio with Camera Stream on iOS.
20-angular-services
Angular service rules for wrapping web-serial-rxjs.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.