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 baleen37/bstack/plugin install meWrote 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/baleen37/bstack/create-pr)<a href="https://agentmods.dev/skills/baleen37/bstack/create-pr"><img src="https://agentmods.dev/badge/skills/baleen37/bstack/create-pr/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/baleen37/bstack/create-pr"><img src="https://agentmods.dev/badge/skills/baleen37/bstack/create-pr.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.00016 | $0.00417 |
| Opus 5.5 | $0.00006 | $0.00167 |
| Sonnet 5.5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
create-pr 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
Run these lines as written. The scripts carry the tested sync and merge-wait logic; do not reimplement them:
S="${CLAUDE_PLUGIN_ROOT}/skills/create-pr/scripts"
# If on main/master: checkout -b <type>/<short> first
git add <files> && git commit -m "type(scope): msg"
"$S/preflight-check.sh" # after the commit: syncs if behind base (needs a clean tree)
git push -u origin HEAD
gh pr create --title "$(git log -1 --pretty=%s)" --body "<body>"
# Auto merge: only if user explicitly requests it
# gh pr merge --auto --squash
# Watch checks via the Monitor tool so per-check events and the terminal event stream as notifications.
# Monitor({command: "\"$S/wait-for-merge.sh\"", description: "PR checks", timeout_ms: 1800000, persistent: false})
wait-for-merge.sh only observes; it never merges. Merging happens only through
gh pr merge --auto --squash, and only when the user asked for it. Each check: <name>: <bucket>
line streams as a notification; the terminal event has one of these prefixes — branch on it:
MERGED:→ doneAWAITING_REVIEW:→ CI green, not merged (no auto merge enabled, or a reviewer is required)CI_FAILED: <url> run-id=<id>→gh run view <run-id> --log-failed→ fix the failure once → commit, push → re-enablegh pr merge --auto --squashif it was requested → re-invoke Monitor. Stop if unclear or still failing.CLOSED:→ stop.
PR body: fill PR template if exists, else summary+changes+tests.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +1 lines d65ceaacfcb3
- 1mo ago First seen · 32 lines · 16 tokens per session scan A 8226efeaf6f7
create-pr is a skill published in the GitHub repository baleen37/bstack (4 stars, last pushed 18d ago), licensed MIT. It adds 16 tokens to every session and 417 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
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.