com-example-legacy-LegacyBridgeService

com-example-legacy-LegacyBridgeService is a cursor rule for Cursor from PIsberg/vibetags. It costs 0 tokens per session (138 once invoked), scanned A, original, MIT.

Coding rules for a compatibility service that connects current code to an older mainframe system, including its unusual data format.

In plain words
What is it for?
Changing only explicitly requested business logic while preserving the existing compatibility bridge and its unescaped KEY=…;VAL=… wire format.
Why use it?
They prevent well-intentioned structural changes from breaking the exact format and behavior expected by the older system.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Changing only explicitly requested business logic while preserving the existing compatibility bridge and its unescaped KEY=…;VAL=… wire format.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/pisberg/vibetags/com-example-legacy-legacybridgeservice
Install

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.

Clone the repo
git clone --depth 1 https://github.com/PIsberg/vibetags

Made for: Cursor.

Wrote 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.

agentmods badge for com-example-legacy-LegacyBridgeService

README.md
[![agentmods](https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-legacy-legacybridgeservice/github.svg)](https://agentmods.dev/rules/pisberg/vibetags/com-example-legacy-legacybridgeservice)
Your own site
<a href="https://agentmods.dev/rules/pisberg/vibetags/com-example-legacy-legacybridgeservice"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-legacy-legacybridgeservice/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.

agentmods 80×15 button for com-example-legacy-LegacyBridgeService

Your own site · 80×15
<a href="https://agentmods.dev/rules/pisberg/vibetags/com-example-legacy-legacybridgeservice"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-legacy-legacybridgeservice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 138 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00138
Opus 5 $0.00000 $0.00069
Sonnet 5 $0.00000 $0.00028
Haiku 4.5 $0.00000 $0.00014

Measured 10d ago against content hash 66ed826e39ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

com-example-legacy-LegacyBridgeService 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 10d 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.

examples/basic/.cursor/rules/com-example-legacy-LegacyBridgeService.mdc · 14 lines

What it actually says

Rules for LegacyBridgeService

Legacy Compatibility Bridge

  • Rule: Compatibility bridge. Do not attempt to modernize, elegant-ize, or refactor structural patterns. Only modify internal business logic as explicitly requested.
  • Reason: Mirrors a quirk in the upstream mainframe wire format (KEY=…;VAL=… with no escaping); 'modernizing' it broke the EBCDIC gateway in 2023
Changes

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.

  1. 10d ago First seen · 14 lines · 0 tokens per session scan A 66ed826e39ff

Subscribe to this mod's changes

com-example-legacy-LegacyBridgeService is a cursor rule published in the GitHub repository PIsberg/vibetags (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 138 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.