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/jsdocgit 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/jsdoc)<a href="https://agentmods.dev/instructions/ocean-industries-concept-lab/openbridge-webcomponents/jsdoc"><img src="https://agentmods.dev/badge/instructions/ocean-industries-concept-lab/openbridge-webcomponents/jsdoc.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.05261 | $0.05261 |
| Opus 5 | $0.02631 | $0.02631 |
| Sonnet 5 | $0.01052 | $0.01052 |
| Haiku 4.5 | $0.00526 | $0.00526 |
Grade A, and why
openbridge-webcomponents jsdoc.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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JSDoc Documentation Rules
The full JSDoc template, the @slot/@fires contract, @availableWhen,
component lifecycle tags, and the three documentation patterns. AGENTS.md § 3
carries the summary; docs/agents/jsdoc.md is the source of truth.
Key points:
- One-line summary with the tag name and a brief description.
- Features / Variants — bullet list of capabilities and configuration options.
- Usage Guidelines — when and how to use the component; contrast with similar components.
- Slots — table of slot names, conditions, and purposes.
- Events — a
@firestag for every event the component exposes, custom and native (a passthrough<button>'sclickincluded). See below. - Properties are documented in the class JSDoc, one tag per public property, without a type —
@property name - description— placed after the Markdown sections and before@slot/@fires. Conditional properties add a line@availableWhen name conditiondirectly under their tag. No inline JSDoc above@property()fields (npm run lint:commentswarns;--fixhoists them). A tag naming a property that does not exist is a ghost manifest member —npm run lint:slotsfails on it. Mixin-provided properties (svghelpers/setpoint-mixin.ts,svghelpers/setpoint-bundle.ts) keep their inline docs. - Tone: Do NOT mention "maritime", "industrial", "bridge", or domain qualifiers; keep text domain-agnostic.
- If purpose is unclear, insert
**TODO(designer)**instead of guessing. @availableWhenfor conditional properties — see below.- Exactly one lifecycle tag on every
@customElementclass — see below.
Component lifecycle tags (@stable / @beta / @experimental / @deprecated)
Every class registered with @customElement carries exactly one lifecycle
tag in its class JSDoc. This tag is the single source of truth for the
component's API maturity — Storybook mirrors it, never the other way around.
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 · 348 lines · 5,261 tokens per session scan A 038e6f81d039
openbridge-webcomponents jsdoc.instructions.md is an instructions file published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (91 stars, last pushed yesterday), licensed Apache-2.0. It adds 5,261 tokens to every session, about $0.0263 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.