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 create-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/create-pr-flow)<a href="https://agentmods.dev/skills/avi1234/claude-team-plugins/create-pr-flow"><img src="https://agentmods.dev/badge/skills/avi1234/claude-team-plugins/create-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/create-pr-flow"><img src="https://agentmods.dev/badge/skills/avi1234/claude-team-plugins/create-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.00349 |
| Opus 5.5 | $0.00006 | $0.00140 |
| Sonnet 5.5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
create-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 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
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. Run Definition of Done
{YOUR_LINT_COMMAND}{YOUR_BUILD_COMMAND}{YOUR_TEST_COMMAND}{YOUR_FORMAT_COMMAND}
If any check fails, STOP and report the error. Do not proceed.
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., {YOUR_TICKET_PREFIX}-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. Check CI
- Check pipeline status for current repo + branch
- If running: poll 60s intervals, max 15 attempts (display "waiting...")
- If failed: show logs, ask for fixes, commit/push after confirmation, re-check
- If success: report "CI passed"
6. Show Final Status
- Display PR URL, state, and CI status
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.
- 1mo ago First seen · 46 lines · 15 tokens per session scan A a35e158cfb47
create-pr-flow is a skill published in the GitHub repository avi1234/claude-team-plugins (5 stars, last pushed 8mo ago), licensed MIT. It adds 15 tokens to every session and 349 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
commit
Analyze git diffs or staged changes and generate conventional commit messages that explain WHY a change was made. Supports auto-detecting type and scope, intelligent file staging, and interactive overrides. Use when asked to "write a commit message", "generate a commit", "describe my changes", "commit this"…
commit-push-pr
Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.
commit
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.
fix-github-issue
Turn one known GitHub issue into a merged pull request, headless: a worker in its own git worktree, a draft pull request carrying its proof, an isolated second-engine reviewer, and a serial pull master that checks import-closure staleness against the base before it merges. Use when the task is "fix issue N…
herdr-agents
Dispatch subagent scopes as real coding agents in Herdr. One git worktree, one workspace, and one named agent per scope. Exchange mail with them, integrate their diffs, and delete the worktrees. Use when running inside Herdr (HERDRENV=1) and the user wants agents in worktrees, Herdr panes, or parallel work on separate…
commit
Create focused conventional commits with a mandatory gitmoji. Use when the user asks to commit, write a commit message, or split changes into commits.