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 skills add rstackjs/agent-skills --skill pr-creatorgit clone --depth 1 https://github.com/rstackjs/agent-skillsWrote 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/rstackjs/agent-skills/pr-creator)<a href="https://agentmods.dev/skills/rstackjs/agent-skills/pr-creator"><img src="https://agentmods.dev/badge/skills/rstackjs/agent-skills/pr-creator/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/rstackjs/agent-skills/pr-creator"><img src="https://agentmods.dev/badge/skills/rstackjs/agent-skills/pr-creator.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.00023 | $0.00484 |
| Opus 5.5 | $0.00009 | $0.00194 |
| Sonnet 5.5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
pr-creator 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.
This is a copy
100% identical to pr-creator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull request creator
Steps
-
Confirm the current branch with
git branch --show-current. If it is the default branch, create and switch to a new branch before doing anything else. Use a descriptive branch name, preferablyfeat-<topic>orfix-<topic>. -
Review local changes with
git status --short. Do not revert unrelated user changes. Before creating the PR, ensure the intended changes are committed and never commit directly on the default branch. -
Read the repository's PR template when available and follow its current headings and guidance.
-
Draft the PR title in the repository's standard format. If the repository uses Conventional Commits, common patterns include:
feat(core): add ...fix(types): ...docs: ...refactor(types): ...chore(ci): ...for CI workflow, check, or release automation changeschore(deps): ...release: v1.2.0
-
Write the PR body in concise, clear English.
- Explain the problem or motivation and why it matters, then describe the approach and resulting behavior.
- Include API, compatibility, or migration details when they help reviewers assess the change.
- Keep typical descriptions to a few short sentences. Focus on the key changes rather than a file-by-file summary.
- Include tests, documentation, and validation required by repository guidelines or the template. Otherwise, mention them only when central to the change or relevant to review risk.
-
Include relevant issue, discussion, or design links alongside the context they support, following the template's guidance. For dependency upgrades, link to the target version's release notes or tag when available.
-
Push the branch only after re-checking the branch name. Never push the default branch directly.
-
Create the PR. When running in Codex, use the Codex GitHub connector/plugin for GitHub operations. Use
gh pr createonly as a fallback when the connector is unavailable.
Constraints
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 7545309b5b4a
- 1mo ago Changed · -8 lines 6bc664470965
- 1mo ago Changed · -18 tokens per session cd9d87f8adb4
- 2mo ago First seen · 57 lines · 41 tokens per session scan A fdb78d1ef2dd
pr-creator is a skill published in the GitHub repository rstackjs/agent-skills (97 stars, last pushed 7d ago), licensed MIT. It adds 23 tokens to every session and 484 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pr-creator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.