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/integration-systemsgit 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/integration-systems)<a href="https://agentmods.dev/instructions/ocean-industries-concept-lab/openbridge-webcomponents/integration-systems"><img src="https://agentmods.dev/badge/instructions/ocean-industries-concept-lab/openbridge-webcomponents/integration-systems.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.00510 | $0.00510 |
| Opus 5 | $0.00255 | $0.00255 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
openbridge-webcomponents integration-systems.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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration System Components
Nine components for the integration surface — the app bar, tabs, and the fleet / vessel selection controls that sit above the instrument panels.
obc-integration-button is the shared primitive
Four of the nine compose it: integration-bar, integration-bar-dropdown,
integration-dropdown-button and integration-vessel-selector. It carries the
family's variant and type enums (IntegrationButtonVariant,
IntegrationButtonType) plus the slot flags — hasLeadingIcon,
hasTrailingIcon, hasTrailingIcon2, hasStatus.
Add a shared visual or interaction concern to the primitive, not to each
consumer. The relationship mirrors obc-watch in the radial family: one place
owns the appearance, the rest configure it.
The remaining four — integration-app-bar, integration-fleet-button,
integration-tabs, integration-vessel-menu — stand alone.
Conventions
- The boolean slot flags follow the repo's positive naming rule, so they
default to
falseand read naturally in templates. Adding a slot means adding a matchinghasXflag and a@slottag — seejsdoc.md. - These are interactive controls, so the keyboard and ARIA obligations in
a11y.mdapply. Dropdowns need arrow-key navigation,Enterto select andEscapeto close, per the APG menu pattern. - Styling follows the standard two-layer touch/visual target model — see
css-postcss.md.
Icon-heavy stories
The integration bar renders many icons, so its stories are among the first to drift when the icon library is regenerated from Figma. After an icon refresh, expect to refresh these baselines:
npx vitest run --project storybook 'integration'
IMPLEMENTATION_GUIDELINES.md § Icons
names integration-bar explicitly as a path needing a baseline update after a
family rename.
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.
- 5d ago First seen · 53 lines · 510 tokens per session scan A 5b87f54535af
openbridge-webcomponents integration-systems.instructions.md is an instructions file published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (92 stars, last pushed today), licensed Apache-2.0. It adds 510 tokens to every session, about $0.0026 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.