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.
npx skills add agentpipe/pipebuilder --skill bugfix-reviewgit 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/skills/agentpipe/pipebuilder/bugfix-review)<a href="https://agentmods.dev/skills/agentpipe/pipebuilder/bugfix-review"><img src="https://agentmods.dev/badge/skills/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/skills/agentpipe/pipebuilder/bugfix-review"><img src="https://agentmods.dev/badge/skills/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.00020 | $0.00067 |
| Opus 5.5 | $0.00008 | $0.00027 |
| Sonnet 5.5 | $0.00004 | $0.00013 |
| Haiku 4.5 | $0.00002 | $0.00007 |
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 2mo 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
Bugfix Review
Reproduce or verify the reported symptom, distinguish evidence from hypotheses, review the affected path, and validate the fix against nearby behavior.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 12 lines · 20 tokens per session scan A 485146945c76
bugfix-review is a skill published in the GitHub repository agentpipe/pipebuilder (3 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 67 once invoked, about $0.0001 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 skills, from other repositories
adjudicate-review
Turn an incoming set of findings — from an AI reviewer, a referee report, a code review, a linter, or a second model — into verified fixes, without letting a confident misread damage correct work. Every finding is a CANDIDATE until checked against the actual source. Use whenever you receive review comments, audit…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
ln-44-performance-optimizer
Profiles and improves a measured performance bottleneck; retains only verified improvements.
ln-71-operations-investigator
Diagnoses incidents from operational evidence and proposes recovery; does not change live systems.
ln-96-error-handling-engineer
Implements safe error boundaries, cancellation and user recovery contracts; not telemetry pipelines or durable retry machinery.
ln-97-observability-engineer
Implements structured diagnostics, correlation and justified metrics or traces; not incident investigation or a mandatory telemetry platform.