automation-components

automation-components is a cursor rule for Cursor from Ocean-Industries-Concept-Lab/openbridge-webcomponents. It costs 0 tokens per session (3,260 once invoked), scanned A, original, Apache-2.0.

Rules for creating automation schematic components such as motors, pumps, valves, pipes, tanks, readouts, and badges. These are reusable interface elements for showing or controlling equipment.

In plain words
What is it for?
Use them when adding or changing automation components, including on/off controls, speed controls, position selectors, HVAC tiles, and display-only elements.
Why use it?
They specify which base component and state properties each type of device should use, keeping new components consistent with the existing system.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/ocean-industries-concept-lab/openbridge-webcomponents/automation-components
Clone the repo
git clone --depth 1 https://github.com/Ocean-Industries-Concept-Lab/openbridge-webcomponents

Made for: Cursor.

Wrote 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.

agentmods badge for automation-components

README.md
[![agentmods](https://agentmods.dev/badge/rules/ocean-industries-concept-lab/openbridge-webcomponents/automation-components.svg)](https://agentmods.dev/rules/ocean-industries-concept-lab/openbridge-webcomponents/automation-components)
Your own site
<a href="https://agentmods.dev/rules/ocean-industries-concept-lab/openbridge-webcomponents/automation-components"><img src="https://agentmods.dev/badge/rules/ocean-industries-concept-lab/openbridge-webcomponents/automation-components.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,260 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03260
Opus 5 $0.00000 $0.01630
Sonnet 5 $0.00000 $0.00652
Haiku 4.5 $0.00000 $0.00326

Measured 5d ago against content hash 55b78a5a5693, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

automation-components 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 5d 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.

.cursor/rules/automation-components.mdc · 165 lines

How it starts

The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Automation Components Instructions

These instructions apply to all automation schematic components: motorized devices (pump, motor, fan), valves, electrical components, line/pipe elements, tanks, readouts, and badges.

Base Class Hierarchy

Choose the correct base class when creating a new automation device:

Use case Base class State properties
Motorized device (on + speed) ObcAbstractAutomationButtonMotorized on, speed + speedUnit (default %) + speedMaxDigits (default 3); speedInPercent is deprecated
Binary on/off device ObcAbstractAutomationButtonSquared on
Analog device with value ObcAbstractAutomationButton + custom logic open, value (0–100)
Position selector (shuffle) ObcShuffleButtonBase selectedPosition, vertical; fires position-selected (see § Shuffle selectors)
HVAC tile (specialty tank) ObcAbstractSpecialtyTank medium, static, showIcon, tag; tank-style positioning, clickable, activated, badges, alert
Pure display (no button) LitElement directly N/A

All button-based components share ObcAbstractAutomationButton as root, which provides: positioning, readout stacks, badges, alert frames, tags, and label direction.

Read the full file on GitHub · 165 lines

Changes

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.

  1. 5d ago First seen · 165 lines · 0 tokens per session scan A 55b78a5a5693

Subscribe to this mod's changes

automation-components is a cursor rule published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (92 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,260 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-30.