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/agentpipe/pipebuilderWrote 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/agentpipe/pipebuilder/bugfix-review)<a href="https://agentmods.dev/rules/agentpipe/pipebuilder/bugfix-review"><img src="https://agentmods.dev/badge/rules/agentpipe/pipebuilder/bugfix-review/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/agentpipe/pipebuilder/bugfix-review"><img src="https://agentmods.dev/badge/rules/agentpipe/pipebuilder/bugfix-review.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.00041 | $0.00041 |
| Opus 5.5 | $0.00016 | $0.00016 |
| Sonnet 5.5 | $0.00008 | $0.00008 |
| Haiku 4.5 | $0.00004 | $0.00004 |
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 1mo 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.
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.
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.
- 1mo ago First seen · 7 lines · 41 tokens per session scan A 4e69e77e1c0b
bugfix-review is a cursor rule published in the GitHub repository agentpipe/pipebuilder (3 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session, about $0.0002 per session on Opus 5.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.
Other cursor rules, from other repositories
e2e-testing
E2E Flow Tests setup and debugging guide.
common-fixes
Utility for VAN QA common validation fixes.
hatch3r-dynamic-stack-verification
Runtime-evidence gates for stacks with no static type layer (plain-JS Vue, dynamic persistence) — smoke-mount changed components, dormant-collection-read ratchet, runtime smoke evidence on module-boundary changes; a green lint+build+mock-suite proves a layer, not the system.
roslyn-mcp-pitfalls
Known pitfalls and regression lessons from production use.
debug-issue
When the user reports a bug, an error, or unexpected behavior. Enforces four structured phases — reproduction, failing test, root cause isolation, fix and verify — to stop guess-and-check loops.
debugging-and-testing-rules
description: Specifies practices for debugging and testing, including logging, unit tests, and ensuring all tests pass. globs: /.