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 hamzaPixl/pixl-ai --skill pr-creationgit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/pr-creation)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/pr-creation"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/pr-creation/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/hamzapixl/pixl-ai/pr-creation"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/pr-creation.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.00036 | $0.00684 |
| Opus 5.5 | $0.00014 | $0.00274 |
| Sonnet 5.5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
pr-creation 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Complete PR creation workflow: analyze changes, wrap into conventional commits, rebase on base branch, generate changelog entries, and create the pull request with a structured description.
Why small, well-described PRs matter: PRs under 400 lines get reviewed 3x faster and receive higher-quality feedback. A clear description that explains why (not just what) helps future readers understand intent when git-blaming months later.
Required References
Before starting, read these files:
references/standards/commit-conventions.md— commit message format and conventionsreferences/standards/pr-best-practices.md— PR description structure and review guidelines
Step 1: Discovery
- Analyze
git diff(staged + unstaged changes) - Identify the base branch (main/master/develop)
- Check for existing changelog file
- Determine commit convention (conventional commits)
- Identify related issues or tickets
Step 2: Wrap Changes
- Group related changes into logical units
- Stage files that belong together
- Ensure no unrelated changes are included
- Check for files that shouldn't be committed (.env, credentials)
Step 3: Commit
- Create conventional commit messages (feat/fix/refactor/docs/test/chore)
- Include scope and description
- Add body with details if commit is non-trivial
- Reference issues in footer
Step 4: Rebase
- Fetch latest base branch
- Rebase feature branch on base
- Resolve any merge conflicts
- Verify tests still pass after rebase
Step 5: Changelog (Conditional)
Only if changelog file exists.
- Generate changelog entries from commits
- Follow existing changelog format
- Group by type (Added, Changed, Fixed, Removed)
Step 6: Create PR
- Push branch to remote
- Create PR with structured description:
- Summary (1-3 bullet points)
- Changes made
- Test plan
- Screenshots (if UI changes)
- Add labels and reviewers if configured
Gotchas
- Always rebase onto the target branch before creating the PR — stale branches cause merge conflicts that block reviewers and CI
gh pr createfails silently if the branch has not been pushed — always push with-ufirst to set the upstream tracking branch- Use draft PRs (
--draft) for work-in-progress — this prevents accidental review requests and signals the PR is not yet ready for feedback - Changelog updates should go in a separate commit from code changes — mixing them makes reverts harder and pollutes the diff reviewers need to focus on
- Never force-push after PR review has started — it destroys review comments and makes it impossible for reviewers to see what changed since their last review
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 · 76 lines · 36 tokens per session scan A 299bce4c45a5
pr-creation is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 684 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-09-03.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…