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 commands/aziontech/webkit/open-prgit clone --depth 1 https://github.com/aziontech/webkitWhat 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.00048 | $0.01488 |
| Opus 5 | $0.00024 | $0.00744 |
| Sonnet 5 | $0.00010 | $0.00298 |
| Haiku 4.5 | $0.00005 | $0.00149 |
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 yesterday.
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 — 71 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.
If the diff spans multiple packages, prefer one commit per scope (CONTRIBUTING: "one package per commit when possible").
2. Related issue (optional)
- Ask: "Which issue does this relate to? (
ENG-1234, or leave blank if none)". With an issue, the tag goes in the subject, after the colon (fix(webkit): [ENG-1234] …) — never before the type. No issue → no tag — never write[NO-ISSUE](dead characters; commitlint rejects it).
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.
- yesterday First seen · 71 lines · 48 tokens per session scan A 575f07f40538
open-pr is a command published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 1,488 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 commands, from other repositories
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
diagnose
Run sivtr doctor to check the environment, then investigate any failing checks.
test-changed
Run the full quality gate on only the files changed since branching from main.
route
Route notes from inbox to appropriate vault destinations.
cleanup-transcript
Clean up a video/audio transcript (SRT or plaintext) - identifies structure, fixes transcription errors, asks clarifying questions iteratively.