Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add baodq97/open-plugin/plugin install vbounceWrote 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/commands/baodq97/open-plugin/bugfix)<a href="https://agentmods.dev/commands/baodq97/open-plugin/bugfix"><img src="https://agentmods.dev/badge/commands/baodq97/open-plugin/bugfix/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/commands/baodq97/open-plugin/bugfix"><img src="https://agentmods.dev/badge/commands/baodq97/open-plugin/bugfix.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.00014 | $0.00189 |
| Opus 5.5 | $0.00006 | $0.00076 |
| Sonnet 5.5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
bugfix 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
Start a V-Bounce bugfix cycle for P2/P3 bugs. User must provide a ticket ID.
Instructions
- Read
${CLAUDE_PLUGIN_ROOT}/skills/vbounce/references/workflows-bugfix-track.mdfor the full bugfix workflow - Generate cycle ID:
BF-{PROJECT}-{YYYYMMDD}-{SEQ} - Create workspace:
mkdir -p .vbounce/cycles/{cycle_id}/{triage,fix-plan,fix,review,verify,deploy,knowledge,quality-gates} - Initialize
{workspace}/state.yamlfor bugfix track with phases: triage, fix-plan, fix, review, verify, deploy - Set active cycle in
.vbounce/state.yaml - Begin Triage phase
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 · 16 lines · 14 tokens per session scan A f9e19856ae91
bugfix is a command published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 189 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 commands, from other repositories
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact. Scope it to a release's changes with a git range ( .. ) or changes for the uncommitted working tree; audit the whole repository for the first…
five-whys
Use the "Five Whys" root cause analysis technique to deeply understand problems.
green
Make everything green — fix failing tests and type/compile errors with minimal, real changes and re-run until the suite and types pass. No fake-green.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.