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 agents/ocean-industries-concept-lab/openbridge-webcomponents/building-blocksgit 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/agents/ocean-industries-concept-lab/openbridge-webcomponents/building-blocks)<a href="https://agentmods.dev/agents/ocean-industries-concept-lab/openbridge-webcomponents/building-blocks"><img src="https://agentmods.dev/badge/agents/ocean-industries-concept-lab/openbridge-webcomponents/building-blocks.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.00012 | $0.02535 |
| Opus 5 | $0.00006 | $0.01267 |
| Sonnet 5 | $0.00002 | $0.00507 |
| Haiku 4.5 | $0.00001 | $0.00253 |
Grade A, and why
building-blocks 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 6d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Blocks & SVG Helpers
These instructions apply to SVG-based building block components (instrument-linear, bar-vertical, etc.) and their shared SVG helper utilities.
Agent Safety Rules (Context + Mirroring)
When implementing changes in this area, avoid narrow/local fixes that can introduce regressions:
-
Always load the full file into context before editing
- Read the entire file you are about to change (not just snippets) so you understand how helpers, state, rendering, and events fit together.
- This is required to avoid “local fixes” that miss related logic and accidentally introduce new bugs.
-
Always think in mirrored / generalized layouts (sides + orientations)
- For components like:
packages/openbridge-webcomponents/src/building-blocks/external-scale/external-scale.tspackages/openbridge-webcomponents/src/building-blocks/bar-horizontal/bar-horizontal.tspackages/openbridge-webcomponents/src/building-blocks/bar-vertical/bar-vertical.tspackages/openbridge-webcomponents/src/building-blocks/chart-line/chart-line-base.tspackages/openbridge-webcomponents/src/bars-graphs/line-graph/line-graph.tspackages/openbridge-webcomponents/src/bars-graphs/area-graph/area-graph.ts
- If a task changes behavior for one side (e.g. right), validate the equivalent behavior for the opposite side (left) and for the orthogonal orientation (top/bottom) where applicable.
- Prefer implementing via shared helpers/config so “all sides / all orientations” stay consistent.
- For components like:
packages/openbridge-webcomponents/src/building-blocks/**
When working with building block components in this directory:
- SVG-Based Architecture:
- Building blocks are pure SVG components rendered using Lit's
svgtemplate tag - Components typically render into a
<svg>element with a viewBox for coordinate system control - Use shared helpers from
svghelpers/for coordinate transformations and rendering utilities - Consider checking existing building blocks (e.g.,
instrument-linear) for similar patterns before implementing new features
- Building blocks are pure SVG components rendered using Lit's
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.
- 6d ago First seen · 200 lines · 12 tokens per session scan A a8d0b790b044
building-blocks is an agent published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (92 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 2,535 once invoked, about $0.0001 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 agents, from other repositories
angular-patterns
// Optional with default value readonly name = input ('').
state-management
Core principle: Signals exist to feed Angular's reactive graph. If a value has no reactive consumer, making it a signal adds tracking overhead for no benefit.
webc-generator
The webc-generator is an NX executor that automatically converts UI5 Web Components into Angular-native wrapper components. It eliminates manual maintenance of 100+ component wrappers by reading a Custom Elements Manifest (CEM) and generating the full library from it.
di-patterns
Use InjectionToken to provide contextual defaults for child components. This pattern allows parent components to influence default values without directly manipulating child component inputs.
testing-guidelines
Agent "testing-guidelines" from SAP/fundamental-ngx, covering testing guidelines, test commands, run all tests in a library, run specific test file and examples.
breaking-changes
A breaking change is any modification that could cause existing consumer code to fail or behave differently after upgrading.