Borrowing it
Nothing to install: this file belongs to aziontech/webkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aziontech/webkit/main/.claude/commands/open-pr.mdgit clone --depth 1 https://github.com/aziontech/webkitWrote 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/commands/aziontech/webkit/open-pr)<a href="https://agentmods.dev/commands/aziontech/webkit/open-pr"><img src="https://agentmods.dev/badge/commands/aziontech/webkit/open-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/commands/aziontech/webkit/open-pr"><img src="https://agentmods.dev/badge/commands/aziontech/webkit/open-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.00048 | $0.01783 |
| Opus 5.5 | $0.00019 | $0.00713 |
| Sonnet 5.5 | $0.00010 | $0.00357 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
open-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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /open-pr. Land the current working changes as a pull request against main, following the repo's commit + versioning conventions end to end.
User input: $ARGUMENTS
Source of truth
- Commit format and type→release mapping:
CONTRIBUTING.md§ Commit convention,commitlint.config.js, andrelease-types.md. - Release automation:
release-please-config.json— merges tomainupdate the pending Release PR; merging the Release PR cuts the version. Stock release-please: onlyfeat/fix/ breaking release.
Steps
0. Preflight
- Run
git fetch origin --pruneandgit status. If there is nothing to commit and nothing unpushed → tell the user there is nothing to open a PR for, and stop.
1. Analyze the diff (drives the version bump)
Run git diff (staged + unstaged) and determine, from the change itself:
- type →
feat(new component / prop / event / slot / public export),fix(bug, a11y, visual regression — anything that must ship),refactor,perf,docs,style,chore,test,ci,revert. Release effect (release-please):feat→minor;fix→patch; breaking→major; every other type → no release on its own (urgent production fixes arefix— there is nohotfixtype). - scope → the package without its namespace (
webkit,theme,icons), inferred from the changed paths. - breaking? → a removed or renamed public prop, event, slot, or export ⇒ major. Mark it with
!and aBREAKING CHANGE:footer. Confirm with the user before marking a change breaking.
1b. Version gate — before any commit or PR
State the bump the change will produce for each touched package (major / minor / patch / none), derived from step 1 plus any commit already on the branch (git log origin/main..HEAD — a ! or BREAKING CHANGE: anywhere in the branch makes the squash-merged PR a major).
major: stop. Ask the user explicitly: "This will release a major of@aziontech/<scope>(<current>→<next>). Is that what you want?" Do not commit, push, or open the PR until they answer yes. If they say no, drop the!/footer and re-derive the type, or split the breaking part into its own PR the user chooses to open.minor/patch/none: state it and continue; the plan in step 5 shows it again.
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 · +8 lines 5c7e28355571
- 2mo ago First seen · 71 lines · 48 tokens per session scan A 575f07f40538
open-pr is a command published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,783 once invoked, about $0.0002 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 commands, from other repositories
scm
SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
commit
Automatically generate commit message based on changes and push to current branch. Analyzes git diff to create meaningful commit following conventional commits format. Optionally creates and pushes a git tag.
stable
First, run the /save command to commit all current changes.
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
commit-push-pr
Commit, push, and open a PR (includes changeset creation).