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 agentmods add commands/baodq97/open-plugin/bugfixgit clone --depth 1 https://github.com/baodq97/open-pluginWhat 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 | $0.00014 | $0.00189 |
| Opus 5 | $0.00007 | $0.00095 |
| Sonnet 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 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.
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.
- yesterday 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 3mo ago), licensed MIT. It adds 14 tokens to every session and 189 once invoked, about $0.0001 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.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
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.
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
analyze-test
Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.