openbridge-webcomponents watch-radial-instruments.instructions.md

Architecture instructions for circular watch-style instruments such as compasses, heading displays, rudders, wind indicators, and gauges. They explain which rendering logic belongs in the shared watch renderer and which logic stays specific to one instrument.

In plain words
What is it for?
Use them when adding or changing radial instrument visuals, shared circular elements, layering, or calculations that several instruments use.
Why use it?
They reduce inconsistent changes across related instruments and make the impact of editing shared drawing code clear.

Instructions file for GitHub Copilot

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 instructions/ocean-industries-concept-lab/openbridge-webcomponents/watch-radial-instruments
Clone the repo
git clone --depth 1 https://github.com/Ocean-Industries-Concept-Lab/openbridge-webcomponents

Made for: GitHub Copilot.

Per session 10,138 This file is loaded in full into every session.
When invoked 10,138 The same file — it is already loaded in full.
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 $0.10138 $0.10138
Opus 5 $0.05069 $0.05069
Sonnet 5 $0.02028 $0.02028
Haiku 4.5 $0.01014 $0.01014

Measured yesterday against content hash 01a999e979c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openbridge-webcomponents watch-radial-instruments.instructions.md 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 yesterday.

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.

.github/instructions/watch-radial-instruments.instructions.md · 763 lines

How it starts

The opening of the file, as written. The whole thing — 763 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.tsinstrument-radial.tscompass.tsheading.tsrudder.tswind.tsspeed-gauge.tsgauge-radial.tsazimuth-thruster.tsroll.tsrot-sector.ts

When implementing a new feature or changing existing behavior:

  1. 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-sector owns its bespoke FOV compression, and pitch/roll/pitch-roll/pitch-roll-heave own their coupled buildFrame contracts (see "Shared frame computation"). Do not move those into the shared renderer — doing so changes every other instrument.
  2. Changes to watch.ts affect ALL instruments that use it
  3. If adding a new visual element, add it to watch.ts as a configurable option, not to individual instruments
  4. Navigation instruments are thin wrappers that configure obc-watch and add domain-specific overlays
  5. instrument-radial.ts is a reusable building block that wraps obc-watch for generic gauge use cases

Before completing any change, verify:

  • watch.ts has 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:

Read the full file on GitHub · 763 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. yesterday First seen · 763 lines · 10,138 tokens per session scan A 01a999e979c1

Subscribe to this mod's changes

openbridge-webcomponents watch-radial-instruments.instructions.md is an instructions file published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (91 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10,138 tokens to every session, about $0.0507 per session on Opus 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-08-30.