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/external-scalegit 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/external-scale)<a href="https://agentmods.dev/agents/ocean-industries-concept-lab/openbridge-webcomponents/external-scale"><img src="https://agentmods.dev/badge/agents/ocean-industries-concept-lab/openbridge-webcomponents/external-scale.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.00011 | $0.04426 |
| Opus 5 | $0.00005 | $0.02213 |
| Sonnet 5 | $0.00002 | $0.00885 |
| Haiku 4.5 | $0.00001 | $0.00443 |
Grade A, and why
external-scale 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
External Scale & Bar/Gauge Components
These instructions apply to the external scale renderer and its thin wrapper components (bar-vertical, bar-horizontal, gauge-vertical, gauge-horizontal, gauge-trend).
⚠️ IMPORTANT: Interconnected Components
All components in this system are tightly interconnected and share a common API surface:
external-scale.ts↔bar-vertical.ts↔bar-horizontal.ts↔gauge-vertical.ts↔gauge-horizontal.ts↔gauge-trend.tsWhen implementing a new feature or changing existing behavior:
- Changes must cascade through ALL related components to maintain consistency
- All wrappers expose similar properties with orientation-specific naming (e.g.,
height/width,paddingTop/paddingLeft)- If you add a property to
bar-vertical, you likely need to add the equivalent tobar-horizontal,gauge-vertical,gauge-horizontal,gauge-trendandexternal-scale- If you add a config option to
external-scale.ts, all wrappers need to expose and pass it- Gauge variants (
gauge-vertical/gauge-horizontal/gauge-trend) may intentionally NOT expose certain properties (they use fixed values)Before completing any change, verify:
external-scale.tshas the core logic/configbar-vertical.tsexposes and maps the property correctlybar-horizontal.tshas the mirrored equivalentgauge-vertical.ts/gauge-horizontal.ts/gauge-trend.tsare updated if applicable- All components remain API-consistent
Architecture Overview
The external scale system follows a renderer + wrapper pattern:
┌─────────────────────────────────────────────────────────────────┐
│ external-scale.ts │
│ (Pure SVG renderer - all logic lives here) │
│ • computeExternalScaleLayout() │
│ • renderExternalScale() │
│ • Layout calculations, coordinate mapping, theming │
└─────────────────────────────────────────────────────────────────┘
▲
│ imports
┌──────────────────────┼─────────────────────┬─────────────────────────┐
│ │ │ │
▼ ▼ ▼ ▼
┌──────────────┐ ┌──────────────┐ ┌──────────────────────┐ ┌────────────────────┐
│ bar-vertical │ │bar-horizontal│ │ gauge-vertical/horiz │ │ gauge-trend │
│ (Thin │ │ (Thin │ │ (Fixed-config thin │ │ (Fixed-config thin │
│ wrapper) │ │ wrapper) │ │ wrappers) │ │ wrapper) │
└──────────────┘ └──────────────┘ └──────────────────────┘ └────────────────────┘
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 · 366 lines · 11 tokens per session scan A e3a958c3be48
external-scale is an agent published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (91 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 4,426 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.
nx-workflow
Purpose: Understanding the NX monorepo structure, development patterns, and best practices. For commands, see docs/internal/commands.md.
breaking-changes
A breaking change is any modification that could cause existing consumer code to fail or behave differently after upgrading.