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/vercel/next.js/create-prnpx skills add vercel/next.js --skill create-prgit clone --depth 1 https://github.com/vercel/next.jsWhat 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.00083 | $0.00903 |
| Opus 5 | $0.00042 | $0.00451 |
| Sonnet 5 | $0.00017 | $0.00181 |
| Haiku 4.5 | $0.00008 | $0.00090 |
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 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Use this skill when turning local work into a GitHub pull request.
Fork PRs vs Branch PRs
Before writing a PR description, check whether this is a branch PR (the
branch lives in vercel/next.js) or a fork PR (an external contribution from
a fork). You may write full descriptions for branch PRs, but not for fork
PRs — inform the user, offer to review their description or provide technical
details, and give them the GitHub URL to create the PR themselves. See
"GitHub Pull Requests and Issues" in AGENTS.md for the full policy.
Workflow
-
Inspect the current state before mutating Git:
git status --short git branch --show-current git diff -- <paths>Stage only files that belong to the requested change. Preserve unrelated user changes.
-
Create or confirm the branch:
git switch -c codex/<short-topic>Use the
codex/prefix unless the user asks for a different name. If a.git/*lockorOperation not permittederror appears, rerun the same Git command with sandbox escalation. Do not assume a branch namespace conflict until checking refs withgit branch --list,git show-ref, orgit for-each-ref. -
Validate and commit:
git add <paths> git diff --cached --check git commit -m "<concise message>"Keep commit messages concise and do not add generated-tool or co-author footers.
-
Push the branch:
git push -u origin <branch> -
Create the PR as a draft unless the user explicitly asks otherwise:
gh pr create --draft --base canary --head <branch> --title "<title>" --body '<body>'For this repo, prefer
canaryas the base branch. If GitHub network access fails in the sandbox, rerun with escalation.
PR Body
Use this PR body format:
## Summary
<what changed and why>
## Verification
- `<command that passed>`
- Not run: `<command>` (`<reason>`)
<!-- NEXT_JS_LLM -->
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 · 120 lines · 83 tokens per session scan A 56bd9a076cf8
create-pr is a skill published in the GitHub repository vercel/next.js (142,020 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 903 once invoked, about $0.0004 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-30.
Other skills, from other repositories
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
theme-component
Add complete theme support for one Recharts component. Invoke with the component name, for example theme-component XAxis.
typescript
Write strongly-typed TypeScript code in Recharts.
example
Create new example charts for Recharts documentation website.
investigate
Find root cause for a bug or an issue in Recharts and propose a solution.