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/testing-visualgit clone --depth 1 https://github.com/Ocean-Industries-Concept-Lab/openbridge-webcomponentsWhat 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.01571 | $0.01571 |
| Opus 5 | $0.00785 | $0.00785 |
| Sonnet 5 | $0.00314 | $0.00314 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
openbridge-webcomponents testing-visual.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 3d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Testing and Storybook Config
Run one component, not the suite
The full snapshot suite is slow and its failures are hard to attribute. Always scope to the component you changed:
npx vitest run --project storybook 'component-name'
Updating baselines — the filter must come BEFORE --update:
npx vitest run --project storybook 'component-name' --update # correct
npx vitest run --project storybook --update 'component-name' # WRONG
Written after the flag, the name is consumed as the flag's value and the full suite runs in update mode, silently rewriting unrelated flaky baselines. This is the single most damaging mistake in this area.
Always re-run without --update afterwards to confirm the new baselines are
stable.
Baselines are environment-sensitive
__vis__/linux/__baselines__/ committed — what CI compares against
__vis__/linux/__results__/ local output, gitignored
__vis__/darwin/__baselines__/ macOS, NOT committed
Only the Linux baselines ship. Regenerating on macOS produces diffs CI will reject.
Prefer the CI path: comment /update-snapshots on the pull request. The
update-snapshots.yml workflow regenerates inside the same Docker image CI
uses and pushes the result to the PR branch. Locally, the Docker route is
npm run test-storybook:docker — see
IMPLEMENTATION_GUIDELINES.md § Docker Testing
and ci-and-release.md.
Storybook config
.storybook/ holds main.ts, preview.tsx, manager.ts (sidebar badges for
the lifecycle tags), openbridgeTheme.ts, and vitest.setup.ts, which wires the
snapshot project.
Two facts that bite:
- Run
npm run analyzebefore testing a new component's stories. Storybook resolves story args to element properties throughcustom-elements.json; without it the args silently never reach the element. - Lifecycle badges are derived, never hand-written.
meta.tagsmirrors the class JSDoc — seejsdoc.md. Tooling tags (autodocs,skip-test,!snapshot) and version tags (6.0,6.1) stay hand-written.
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.
- 3d ago First seen · 144 lines · 1,571 tokens per session scan A 57429f97fbb7
openbridge-webcomponents testing-visual.instructions.md is an instructions file published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (91 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,571 tokens to every session, about $0.0079 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
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
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
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
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.