Borrowing it
Nothing to install: this file belongs to luthersystems/elps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luthersystems/elps/main/.claude/skills/pr/SKILL.mdgit clone --depth 1 https://github.com/luthersystems/elpsWrote 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/luthersystems/elps/pr)<a href="https://agentmods.dev/skills/luthersystems/elps/pr"><img src="https://agentmods.dev/badge/skills/luthersystems/elps/pr/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/luthersystems/elps/pr"><img src="https://agentmods.dev/badge/skills/luthersystems/elps/pr.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.00000 | $0.00787 |
| Opus 5.5 | $0.00000 | $0.00315 |
| Sonnet 5.5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
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 2d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pr — Pull Request Creation Skill
Creates a PR after verifying all checks pass. Handles the full ship workflow: verify, push, create PR.
Trigger
Use when asked to create a PR, submit changes for review, or ship changes.
Workflow
1. Determine Base Branch
gh repo view --json defaultBranchRef -q '.defaultBranchRef.name'
This is typically main.
2. Guard: Verify Not on Main
current=$(git branch --show-current)
if [ "$current" = "main" ] || [ "$current" = "master" ]; then
echo "ERROR: On $current — create a feature branch first"
exit 1
fi
STOP if on main/master. Create a feature branch before proceeding. Never push directly to the default branch.
Run this guard before every commit, not just before pushing: git checkout main && git pull mid-session leaves you on main, and the next commit lands there. git branch --show-current is cheap.
3. Fetch and Rebase
git fetch origin
git rebase origin/<base-branch>
If there are conflicts, resolve them before proceeding.
4. Run Full Verification
Run the complete /verify pipeline. If any step fails, stop and fix before creating the PR.
5. Push
git push -u origin <current-branch>
6. Create the PR
gh pr create --title "<concise title>" --body "$(cat <<'EOF'
## Summary
- <bullet point describing what changed>
- <bullet point describing why>
## Test Plan
- [ ] `/verify` pipeline passes (tests, race, elpscheck, static-checks, elpsvet, fmt, lint, doc)
- [ ] <change-specific checks>
Closes #<N>
EOF
)"
7. Report
Return the PR URL so the user can review it.
PR Title Guidelines
- Keep under 70 characters
- Use imperative mood: "Add ...", "Fix ...", "Update ..."
- Be specific: "Add rethrow builtin for handler-bind" not "Add new feature"
PR Body Guidelines
- Summary: 1-3 bullet points explaining what and why
- Test Plan: Checklist of verification steps
- Closes #N: Link to the issue if this PR resolves one
- End with the attribution line your session instructions specify
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.
- 2d ago First seen · 106 lines · 0 tokens per session scan A 06a6aaade2ea
pr is a skill published in the GitHub repository luthersystems/elps (36 stars, last pushed today), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 787 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-10-26.
Other skills, from other repositories
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
gh-labels
Reference for what GitHub issue/PR labels mean in this workspace (S-triage, S-needs-scope, S-impl, prio-p0-critical, A-ext-dev-tools, A-perf, A-ux, and others under My Labels). Use when the user asks what a label means, which label to apply, or how to add missing labels to a repo. Secondary: bootstrap labels on a new…
gh-pr
Writes clear pull request descriptions from the current branch diff against a base branch. Defaults to main, but supports dev or any other user-specified comparison branch. Use when the user asks for a PR description, pull request summary, or a markdown write-up for changes against a base branch.
gh-rev
Use the gh-rev CLI to maintain a persistent Markdown review ledger for local branches and pull requests. Trigger when the user names gh-rev, asks to save or submit a durable review, inspect or implement existing findings, continue an independent review pass, or adopt branch history into a PR. Use the gh-pr-review…
gh-ci-watch
Watch GitHub PR checks with gh, poll until green/failure/timeout, fetch failed GitHub Actions logs, save logs locally, summarize actionable CI failures, and apply trivial local fixes when safe. Use when the user asks to watch PR checks, wait for CI, inspect failed actions, fix obvious CI failures, or summarize gh pr…