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/Ocean-Industries-Concept-Lab/openbridge-webcomponentsWrote 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/ocean-industries-concept-lab/openbridge-webcomponents/instrument-indicators)<a href="https://agentmods.dev/rules/ocean-industries-concept-lab/openbridge-webcomponents/instrument-indicators"><img src="https://agentmods.dev/badge/rules/ocean-industries-concept-lab/openbridge-webcomponents/instrument-indicators.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.01272 |
| Opus 5 | $0.00000 | $0.00636 |
| Sonnet 5 | $0.00000 | $0.00254 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
instrument-indicators 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 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.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instrument Indicators
Seventeen compact glyphs that convey one value at a glance, sized for strips, lists and tiles rather than for a full instrument panel.
The family boundary is not a code construct — it comes from the Storybook
Indicators/ group, which is the curated product taxonomy. Note
propulsion-tunnel-thruster belongs here despite its name; the taxonomy's
judgement wins over the naming.
They redraw; they do not wrap
This is the single most important fact, and the one that most invites a wrong assumption. An indicator is not a shrunken instance of its full-size counterpart:
- None extends a shared base class — all extend
LitElementdirectly. - None composes
obc-instrument-field. - None renders the full instrument.
obc-rot-indicatorimportsRateOfTurnControllerfrom../rate-of-turn/— the domain logic — and then draws its own SVG. It does not render<obc-rate-of-turn>.
So the shared contract is a convention, not an inheritance hierarchy.
Changing a full instrument does not change its indicator, and vice versa. Ten
pairs share a base name (compass, gauge-radial, gauge-trend, heading,
heave, main-engine, pitch, roll, rudder, wind), and keeping them
visually consistent is a manual obligation.
When a value-to-angle or value-to-state mapping already exists as a controller on the full instrument, import the controller rather than reimplementing the maths. That is the one thing that should be shared.
The canvas convention
Most indicators draw on a 48 × 48 canvas via a local VIEW_SIZE constant.
Two deviate deliberately — pitch-indicator and roll-indicator declare
VIEW_SIZE = 36 for their inner scale, with the outer frame still at 48.
Hosts size themselves from the design token, not from px:
:host {
width: var(--global-size-spacing-touch-target-min);
height: var(--global-size-spacing-touch-target-min);
}
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 · 98 lines · 0 tokens per session scan A fc676ae2de49
instrument-indicators is a cursor rule published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (92 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,272 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.
Other cursor rules, from other repositories
general
Wonder Blocks design system conventions, component patterns, and coding standards.
taste-enforcement
These dials drive all downstream decisions. Adjust per-prompt when the user specifies a different mood.
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.
cli-error-handling
CLI command error handling patterns.