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.
git 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/rules/ocean-industries-concept-lab/openbridge-webcomponents/testing-visual)<a href="https://agentmods.dev/rules/ocean-industries-concept-lab/openbridge-webcomponents/testing-visual"><img src="https://agentmods.dev/badge/rules/ocean-industries-concept-lab/openbridge-webcomponents/testing-visual/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/ocean-industries-concept-lab/openbridge-webcomponents/testing-visual"><img src="https://agentmods.dev/badge/rules/ocean-industries-concept-lab/openbridge-webcomponents/testing-visual.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.03168 |
| Opus 5.5 | $0.00000 | $0.01267 |
| Sonnet 5.5 | $0.00000 | $0.00634 |
| Haiku 4.5 | $0.00000 | $0.00317 |
Grade A, and why
testing-visual 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 8d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 8d ago Changed · +19 lines b07f0fa0d9bf
- 18d ago Changed · +10 lines 3f2ecc777842
- 22d ago Changed · +9 lines 2bf7fa14158a
- 28d ago Changed · +1 lines a9d95e23f8e8
- 1mo ago Changed · +23 lines 17f118262461
- 1mo ago Changed · +52 lines 68f0a3374a47
- 1mo ago First seen · 145 lines · 0 tokens per session scan A 21bf62195b72
testing-visual is a cursor rule published in the GitHub repository Ocean-Industries-Concept-Lab/openbridge-webcomponents (103 stars, last pushed yesterday), with no licence file. It costs nothing until one of its globs matches a file; then it loads 3,168 tokens. 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 cursor rules, from other repositories
always-on
Spec-driven Spring Boot 4 — global guardrails that compensate for Windsurf's lack of a pre-tool-use hook.
production-code
Production code rule — TDD precondition + Spring Boot 4 conventions.
test-code
Test code rule — JUnit 5, Testcontainers, traceability tagging.
issues-testing
Pillar 2 — tiered test execution, impact map, failure workflow.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
development-experience
Dev seed data and local explorability for every feature.