openbridge-webcomponents: Instructions file for GitHub Copilot

.github/instructions/instrument-indicators.instructions.md

openbridge-webcomponents instrument-indicators.instructions.md is an instructions file for GitHub Copilot from Ocean-Industries-Concept-Lab/openbridge-webcomponents. It costs 1,269 tokens per session, scanned A, original, Apache-2.0.

Instructions for compact instrument indicators: small drawings that show one value in strips, lists, or tiles rather than a complete instrument panel. They are separate drawings from full-size instruments.

In plain words
What is it for?
Use them when changing the indicator components, deciding between an indicator and a full instrument, or checking redraw behavior and the shared canvas convention.
Why use it?
They prevent changes to a full instrument and its compact indicator from being assumed to affect each other, and clarify when to use an indicator.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is Ocean-Industries-Concept-Lab/openbridge-webcomponents's own configuration. It tells GitHub Copilot how to work on openbridge-webcomponents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openbridge-webcomponents configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Ocean-Industries-Concept-Lab/openbridge-webcomponents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Ocean-Industries-Concept-Lab/openbridge-webcomponents/develop/.github/instructions/instrument-indicators.instructions.md
Clone the repo
git clone --depth 1 https://github.com/Ocean-Industries-Concept-Lab/openbridge-webcomponents

Made for: GitHub Copilot.

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 openbridge-webcomponents instrument-indicators.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ocean-industries-concept-lab/openbridge-webcomponents/instrument-indicators.svg)](https://agentmods.dev/instructions/ocean-industries-concept-lab/openbridge-webcomponents/instrument-indicators)
Your own site
<a href="https://agentmods.dev/instructions/ocean-industries-concept-lab/openbridge-webcomponents/instrument-indicators"><img src="https://agentmods.dev/badge/instructions/ocean-industries-concept-lab/openbridge-webcomponents/instrument-indicators.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,269 This file is loaded in full into every session.
When invoked 1,269 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.01269 $0.01269
Opus 5 $0.00634 $0.00634
Sonnet 5 $0.00254 $0.00254
Haiku 4.5 $0.00127 $0.00127

Measured 8d ago against content hash 0c6098794544, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

openbridge-webcomponents instrument-indicators.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 8d 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.

.github/instructions/instrument-indicators.instructions.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 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 LitElement directly.
  • None composes obc-instrument-field.
  • None renders the full instrument. obc-rot-indicator imports RateOfTurnController from ../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);
}

Read the full file on GitHub · 97 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. 8d ago First seen · 97 lines · 1,269 tokens per session scan A 0c6098794544

Subscribe to this mod's changes

openbridge-webcomponents instrument-indicators.instructions.md is an instructions file published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (93 stars, last pushed today), licensed Apache-2.0. It adds 1,269 tokens to every session, about $0.0063 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.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens