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 avi1234/claude-team-plugins --skill avi-pr-flowgit clone --depth 1 https://github.com/avi1234/claude-team-pluginsWrote 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/avi1234/claude-team-plugins/avi-pr-flow)<a href="https://agentmods.dev/skills/avi1234/claude-team-plugins/avi-pr-flow"><img src="https://agentmods.dev/badge/skills/avi1234/claude-team-plugins/avi-pr-flow/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/avi1234/claude-team-plugins/avi-pr-flow"><img src="https://agentmods.dev/badge/skills/avi1234/claude-team-plugins/avi-pr-flow.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.00015 | $0.00458 |
| Opus 5 | $0.00008 | $0.00229 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
avi-pr-flow 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 8d 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
You are helping me with a complete PR workflow. Follow these steps:
1. Check Branch Safety
- Get current branch
- If "main" or "master", STOP with error
2. Review Code
- Run
/pr-review-toolkit:review-pr - Fix any suggestions before committing
3. Commit and Push
- Stage all changes
- Generate meaningful commit message from staged diff
- Commit and push to remote
4. Create or Find PR
- Check if PR exists for current branch
- If no PR:
- Extract ticket from branch name (e.g., ME-12345)
- Use $ARGUMENTS as title if provided, otherwise generate:
<ticket>: <summary> - Generate PR body with summary and key modifications
- Create PR and extract PR number
5. Request Bugbot Review
- Comment "bugbot review"
- Poll for bugbot/cursor response (60s intervals, max 5 attempts)
- If timeout, report to me
6. Handle Bugbot Feedback
- Fetch and display all review comments
- If no issues → skip to CircleCI check
- If issues found:
- Ask me to fix and wait for confirmation
- After confirmation: commit, push
- Reply "Fixed! ✅" to all comment IDs
- Request bugbot review again (poll 60s, max 5 attempts)
7. Check CircleCI
- Check pipeline status using CircleCI MCP (current repo + branch)
- If running: poll 60s, max 15 attempts (display "waiting...")
- If failed: show logs, ask for fixes, commit/push after confirmation, re-check
- If success: report "CI passed ✅"
8. Show Final Status
- Display PR state and reviews
Notes
- Stop on any command failure and report error
- Keep me informed at each step
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.
- 8d ago First seen · 59 lines · 15 tokens per session scan A 0569b8fa18e0
avi-pr-flow is a skill published in the GitHub repository avi1234/claude-team-plugins (5 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 458 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 skills, from other repositories
review-responder
Use when receiving feedback on code you implemented, responding to reviewer comments, deciding which review suggestions to implement, or pushing back on incorrect review feedback.
pr-sweep
Use when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR…
open-pr
Use when wrapping up a development task and getting a PR ready — runs local tests, creates a PR (if one doesn't exist) with a structured description template, conducts a code review via the review skill, and checks CI status with quick fixes. Trigger when the user says they're done with a feature, want to open a PR…
review-pr
Review a Pull Request in one of two postures: an expository "tour guide" that walks through changes in logical order, or an adversarial audit that assumes the change is wrong until proven safe and hunts for the failure mode. Triggers: "review PR #123", "adversarial review", "walk me through this PR", "PR tour guide"…
pr-review-fix-pipeline
Autonomous PR review that also applies fixes for non-controversial issues — combines review, fix, test, and commit into a single pipeline. Unlike a read-only review, this writes code. Only use on feature branches where you're comfortable with automatic edits. Trigger on: "review and fix PR", "auto-fix the PR", "clean…
ship
Review, fix, and commit in one run, with a gate before each phase.