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/watch-radial-instruments)<a href="https://agentmods.dev/rules/ocean-industries-concept-lab/openbridge-webcomponents/watch-radial-instruments"><img src="https://agentmods.dev/badge/rules/ocean-industries-concept-lab/openbridge-webcomponents/watch-radial-instruments/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/ocean-industries-concept-lab/openbridge-webcomponents/watch-radial-instruments"><img src="https://agentmods.dev/badge/rules/ocean-industries-concept-lab/openbridge-webcomponents/watch-radial-instruments.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.00000 | $0.10141 |
| Opus 5 | $0.00000 | $0.05071 |
| Sonnet 5 | $0.00000 | $0.02028 |
| Haiku 4.5 | $0.00000 | $0.01014 |
Grade A, and why
watch-radial-instruments 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 9d 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 — 764 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watch & Radial Instruments
These instructions apply to the circular/radial watch-based instrument system, including the core obc-watch renderer and all navigation instruments that use it.
⚠️ IMPORTANT: Interconnected Components
All components in this system are tightly interconnected and share the same rendering core:
watch.ts↔instrument-radial.ts↔compass.ts↔heading.ts↔rudder.ts↔wind.ts↔speed-gauge.ts↔gauge-radial.ts↔azimuth-thruster.ts↔roll.ts↔rot-sector.tsWhen implementing a new feature or changing existing behavior:
- Shared circular rendering belongs in
watch.ts- it is the single source of truth for anything more than one instrument draws. Genuinely component-specific logic stays local:compass-sectorowns its bespoke FOV compression, and pitch/roll/pitch-roll/pitch-roll-heave own their coupledbuildFramecontracts (see "Shared frame computation"). Do not move those into the shared renderer — doing so changes every other instrument.- Changes to
watch.tsaffect ALL instruments that use it- If adding a new visual element, add it to
watch.tsas a configurable option, not to individual instruments- Navigation instruments are thin wrappers that configure
obc-watchand add domain-specific overlaysinstrument-radial.tsis a reusable building block that wrapsobc-watchfor generic gauge use casesBefore completing any change, verify:
watch.tshas the core rendering logic- Helper modules (
tickmark.ts,advice.ts,label.ts, etc.) are updated if needed- All consuming instruments still render correctly
- ViewBox coordination is maintained across layers
- Responsive scaling works at different sizes
Architecture Overview
The watch-based instrument system follows a core renderer + thin wrapper pattern:
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.
- 9d ago First seen · 764 lines · 0 tokens per session scan A d21355768e3a
watch-radial-instruments is a cursor rule published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (95 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 10,141 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
autodarts-patterns
Autodarts Board Manager and adapter-specific patterns.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.