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 vybestack/llxprt-code --skill pr-creatorgit clone --depth 1 https://github.com/vybestack/llxprt-codeWrote 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/vybestack/llxprt-code/pr-creator)<a href="https://agentmods.dev/skills/vybestack/llxprt-code/pr-creator"><img src="https://agentmods.dev/badge/skills/vybestack/llxprt-code/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/vybestack/llxprt-code/pr-creator"><img src="https://agentmods.dev/badge/skills/vybestack/llxprt-code/pr-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00526 |
| Opus 5.5 | $0.00012 | $0.00210 |
| Sonnet 5.5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Creator
This skill guides the creation of high-quality Pull Requests that adhere to the repository's standards.
Workflow
Follow these steps to create a Pull Request:
-
Locate Template: Search for a pull request template in the repository.
- Check
.github/pull_request_template.md - Check
.github/PULL_REQUEST_TEMPLATE.md - If multiple templates exist (e.g., in
.github/PULL_REQUEST_TEMPLATE/), select the most appropriate one based on the context (e.g.,bug_fix.mdvsfeature.md).
- Check
-
Read Template: Read the content of the identified template file.
-
Draft Description: Create a PR description that strictly follows the template's structure.
- Headings: Keep all headings from the template.
- Checklists: Review each item. Mark with
[x]if completed. If an item is not applicable, leave it unchecked or mark as[ ](depending on the template's instructions) or remove it if the template allows flexibility (but prefer keeping it unchecked for transparency). - Content: Fill in the sections with clear, concise summaries of your changes.
- Related Issues: Link any issues fixed or related to this PR (e.g., "Fixes #123").
-
Create PR: Use the
ghCLI to create the PR.gh pr create --title "type(scope): succinct description" --body "..."- Title: Ensure the title follows the Conventional Commits format if the repository uses it (e.g.,
feat(ui): add new button,fix(core): resolve crash).
- Title: Ensure the title follows the Conventional Commits format if the repository uses it (e.g.,
-
** DO NOT CHANGE THE PR DESCRIPTION TO THE LAST THING YOU DID WHEN YOU MAKE CHANGES ** You can amend the PR if the changes you make materially change its behavior but do not change the whole description to just match your last commit. the PR description should be holistic. This is an LLM bad habit that makes it hard to review PRs.
Principles
- Compliance: Never ignore the PR template. It exists for a reason.
- Completeness: Fill out all relevant sections.
- Accuracy: Don't check boxes for tasks you haven't done.
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 First seen · 40 lines · 31 tokens per session scan A 2a2161f5686f
pr-creator is a skill published in the GitHub repository vybestack/llxprt-code (702 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 526 once invoked, about $0.0001 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-30.
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.
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.
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.