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 skills/qte77/claude-code-plugins/creating-pr-from-branchnpx skills add qte77/claude-code-plugins --skill creating-pr-from-branchgit clone --depth 1 https://github.com/qte77/claude-code-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/qte77/claude-code-plugins/creating-pr-from-branch)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/creating-pr-from-branch"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/creating-pr-from-branch.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.00592 |
| Opus 5 | $0.00022 | $0.00296 |
| Sonnet 5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
creating-pr-from-branch 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 4d 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
Create PR from Current Branch
Base branch: $ARGUMENTS (default: main)
Step 1: Analyze Branch
Run using the Bash tool:
git branch --show-current— current branch namegit log --oneline <base>..HEAD— commits to includegit diff --stat <base>..HEAD— overall diff statsgit remote -v— verify remote exists
If no commits ahead of base, stop and inform the user.
Step 2: Generate PR Title and Body
Title: Derive from commits using conventional commit format.
- Single commit: use commit subject as-is
- Multiple commits: synthesize a summary title (
type[(scope)]: description) - Keep under 72 characters
Body: Check for .github/pull_request_template.md. If it exists, populate
its sections. If not, use this minimal format:
## Summary
<1-3 bullet points describing what and why>
## Commits
<list commits from git log>
Body guidelines:
- Fill template checkboxes where applicable (check items that are done)
- Include
Closes #Nif the branch name contains an issue number - Keep it concise — the diff speaks for itself
Step 3: Pause for Approval
Present the title and body. Ask the user:
- Approve: "yes", "y", "create", "go ahead"
- Edit: Provide changes to title or body
- Cancel: "no", "cancel", "stop"
Step 4: Push and Create PR
Once approved:
# Push branch (set upstream)
git push -u origin <branch-name>
# Create PR
# In Codespaces: override token if GH_PAT is needed for cross-repo
gh pr create --base <base> --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
Auth handling: If gh pr create fails with 403/422, retry with
GITHUB_TOKEN="" GH_TOKEN="${GH_PAT}" prefix (Codespaces token override).
After creation, output the PR URL.
Step 5: Post-Create
gh pr view --web— open in browser (optional, ask user)
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.
- 4d ago First seen · 84 lines · 43 tokens per session scan A 2e1f94760201
creating-pr-from-branch is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 43 tokens to every session and 592 once invoked, about $0.0002 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
orchestrator
FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.
flutter-guide
Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.
maestro-flutter
Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
codex-advisor
Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…