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/morpho-org/sdks/pr-creategit clone --depth 1 https://github.com/morpho-org/sdksWhat 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.00000 | $0.01050 |
| Opus 5 | $0.00000 | $0.00525 |
| Sonnet 5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
pr-create 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 today.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-create
Create a draft PR (and a new branch if needed).
Usage
/pr-create
Instructions
You are helping the user create a draft PR quickly. Derive all information from the current changes - do not ask the user any questions.
Step 1: Check Current Branch and Analyze Changes
First, resolve the repo's default branch (the PR will target it), then check what branch the user is on and gather context:
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name)
git rev-parse --abbrev-ref HEAD
git fetch origin "$DEFAULT_BRANCH"
git diff "origin/$DEFAULT_BRANCH" --stat
git diff "origin/$DEFAULT_BRANCH"
Analyze the changes to understand:
- What type of change this is (feat, fix, or chore)
- What the change does (for the PR title and description)
Step 2A: Create New Branch (if on the default branch)
If HEAD is on $DEFAULT_BRANCH, create a new branch based on the changes:
- Derive the branch type from the nature of the changes (feat/fix/chore)
- Derive the branch name from what the changes do (kebab-case, e.g.,
add-dark-mode,fix-login-bug)
Create and push the branch:
git checkout -b <type>/<branch-name>
git push -u origin <type>/<branch-name>
Then proceed to Step 3.
Step 2B: Use Existing Branch (if not on the default branch)
If not on $DEFAULT_BRANCH, use the current branch:
- Extract the branch type from the branch name prefix (feat/, fix/, chore/)
- If the branch doesn't follow this convention, infer the type from the changes
Push the branch:
git push -u origin <branch-name>
Then proceed to Step 3.
Step 3: Commit All Changes
Before creating the PR, commit all uncommitted changes (staged and unstaged). The repo's .gitignore is responsible for keeping .env, key material, and other untracked artefacts out — trust it:
git add -A
git commit -m "<type>: <short description>"
git push
Use the same type and description that will be used for the PR title.
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.
- today First seen · 139 lines · 0 tokens per session scan A 79439c290e7f
pr-create is a command published in the GitHub repository morpho-org/sdks (40 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,050 tokens. 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-09-01.
Other commands, from other repositories
triage
Triage a GitHub issue and present findings on validity, code locations, and optionally create a failing test or resolution plan.
find-issues
Find GitHub issues that a PR might fix.
find-duplicate-prs
Find open PRs that may duplicate a given PR.
upgrade-nodejs
This guide explains how to upgrade the Node.js version that Bun reports for compatibility with Node.js packages and native addons.
add
Scaffolds a feature into a Vendure project — a new plugin or a piece of an existing plugin.
codemod
Runs an automated code transform over a Vendure project.