bugfix-review

A rule requiring bug diagnoses to be supported by observable evidence and followed by a focused regression check. A regression check verifies that a fixed bug does not return.

In plain words
What is it for?
Use it during bug investigations and fixes to verify the diagnosis and test the specific failure again.
Why use it?
It prevents an untested code guess from being reported as the confirmed cause of a bug.

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/agentpipe/pipebuilder/bugfix-review
Clone the repo
git clone --depth 1 https://github.com/agentpipe/pipebuilder

Made for: Cursor.

Per session 41 This file is loaded in full into every session.
When invoked 41 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00041 $0.00041
Opus 5 $0.00020 $0.00020
Sonnet 5 $0.00008 $0.00008
Haiku 4.5 $0.00004 $0.00004

Measured yesterday against content hash 4e69e77e1c0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bugfix-review 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 yesterday.

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/multi-pipeline-project/shared-skills/bugfix-review/.pipe-agents/cursor/.cursor/rules/bugfix-review.mdc · 7 lines

What it actually says

Do not present a static code hypothesis as a verified root cause. Require observable evidence and include a focused regression check.

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. yesterday First seen · 7 lines · 41 tokens per session scan A 4e69e77e1c0b

Subscribe to this mod's changes

bugfix-review is a cursor rule published in the GitHub repository agentpipe/pipebuilder (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session, about $0.0002 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.