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.
npx agentmods add instructions/ocean-industries-concept-lab/openbridge-webcomponents/instruments-miscgit 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/instructions/ocean-industries-concept-lab/openbridge-webcomponents/instruments-misc)<a href="https://agentmods.dev/instructions/ocean-industries-concept-lab/openbridge-webcomponents/instruments-misc"><img src="https://agentmods.dev/badge/instructions/ocean-industries-concept-lab/openbridge-webcomponents/instruments-misc.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 | $0.00983 | $0.00983 |
| Opus 5 | $0.00491 | $0.00491 |
| Sonnet 5 | $0.00197 | $0.00197 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
openbridge-webcomponents instruments-misc.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 4d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instruments Outside the Watch Core
The Instruments/ members that are not driven by obc-watch. Anything that
renders <obc-watch> belongs to
watch-radial-instruments.md instead — check
before assuming a component lives here.
Two distinct groups sit in this file.
Group 1 — borrow watch helpers, draw their own SVG
azimuth-thruster-labeled, depth-actual, draft-trim, heave, thruster
These import helper modules out of watch/ — tickmark.ts, advice.ts,
vessel.ts, vessels.ts — but never render <obc-watch>. They compose their
own SVG around those shared pieces.
The distinction matters when changing a helper: a change to tickmark() or
renderAdvice() reaches these components without going through
obc-watch, so verifying "all watch instruments still render" is not
sufficient. Check this group too.
They are also not bound by the watch viewBox contract — they own their own viewBox and coordinate system, so the "match the viewBox exactly" rule from the watch family does not apply here.
obc-azimuth-thruster-labeled is the composite of the group: it pulls in
badge-command, readout and thruster alongside the watch helpers. Treat it
as a layout shell over those parts rather than an instrument in its own right.
obc-main-engine builds on thruster and shares its thrust-bar vocabulary.
Group 2 — no watch involvement
badge-command, instrument-field, readout-list, readout-list-item,
speed-arrows
obc-instrument-field— the labelled data field used across instrument panels. Two sizes viaInstrumentFieldSize(regular,enhanced). It composesobc-button,obc-navigation-itemand the drop-down icon, so it is interactive: keyboard and ARIA obligations froma11y.mdapply, unlike the display-only instruments around it.obc-readout-list/obc-readout-list-item— a dense row format for tables and lists. The list is a thin container over the items; put shared presentation on the item, not the container.obc-badge-command— a standalone command/state badge with no dependencies at all.obc-speed-arrows— vector arrow art, consumed byobc-speed-indicator. Changing its geometry moves the indicator too.
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.
- 4d ago First seen · 76 lines · 983 tokens per session scan A 5da58c44520f
openbridge-webcomponents instruments-misc.instructions.md is an instructions file published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (91 stars, last pushed today), licensed Apache-2.0. It adds 983 tokens to every session, about $0.0049 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.
Other instructions, from other repositories
fundamental-ngx AGENTS.md
AGENTS.md instructions for SAP/fundamental-ngx, covering angular 22+ development guidelines, persona, quick reference, essential commands and build/lint/test specific library.
fundamental-ngx CLAUDE.md
Claude Code instructions for SAP/fundamental-ngx, covering fundamental ngx, architecture, commands, build / lint / test a library and affected only (prefer this for validation).
primitives CLAUDE.md
Claude Code instructions for radix-ng/primitives, covering radix ng primitives — claude guide, project knowledge, project overview, monorepo structure and naming conventions.
fundamental-ngx copilot-instructions.md
Copilot instructions for SAP/fundamental-ngx, covering github copilot instructions and quick links.
primitives angular.instructions.md
Instructions for radix-ng/primitives, covering typescript best practices, angular best practices, components, state management and templates.
primitives nx.instructions.md
Instructions for radix-ng/primitives, covering general guidelines and generation guidelines.