visbug-buffer-apply

A set of rules for applying changes from a VisBug buffer, which is a temporary list of visual edits. The rules describe how to calculate movement changes and preserve edit identifiers in the original HTML.

In plain words
What is it for?
It is for applying VisBug visual edits to repository files and transferring their identifiers into the source HTML.
Why use it?
It defines how VisBug changes should be applied without blindly copying temporary data into the repository.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/samsebeingener/visbug-mcp-ru/visbug-buffer-apply
Clone the repo
git clone --depth 1 https://github.com/samsebeingener/visbug-mcp-ru

Made for: Cursor.

Per session 77 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 404 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00077 $0.00404
Opus 5 $0.00039 $0.00202
Sonnet 5 $0.00015 $0.00081
Haiku 4.5 $0.00008 $0.00040

Measured 2d ago against content hash 9fb219e64239, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

visbug-buffer-apply 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 2d 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.

.cursor/rules/visbug-buffer-apply.mdc · 37 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 37 lines · 77 tokens per session scan A 9fb219e64239

Subscribe to this mod's changes

visbug-buffer-apply is a cursor rule published in the GitHub repository samsebeingener/visbug-mcp-ru (6 stars, last pushed 1mo ago), with no licence file. It adds 77 tokens to every session and 404 once invoked, about $0.0004 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-31.