Borrowing it
Nothing to install: this file belongs to ScientiaCapital/unsloth-mcp-server. 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/ScientiaCapital/unsloth-mcp-server/main/.claude/commands/pr.mdgit clone --depth 1 https://github.com/ScientiaCapital/unsloth-mcp-serverWrote 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/commands/scientiacapital/unsloth-mcp-server/pr)<a href="https://agentmods.dev/commands/scientiacapital/unsloth-mcp-server/pr"><img src="https://agentmods.dev/badge/commands/scientiacapital/unsloth-mcp-server/pr.svg" alt="Measured on agentmods" 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.00014 | $0.00734 |
| Opus 5 | $0.00007 | $0.00367 |
| Sonnet 5 | $0.00003 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00073 |
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 6d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pr — Clean Pull Request Workflow
You are preparing a PR for: $ARGUMENTS
Instructions
Step 1: Sync with upstream
git fetch origin
git checkout main
git pull origin main
Step 2: Create a clean branch
Slugify the description into a branch name:
git checkout -b feat/$ARGUMENTS_SLUG # or fix/$ARGUMENTS_SLUG
Step 3: Build the feature/fix
Implement what was requested. Follow these rules strictly:
- Read
.claude/rules/coding.mdand follow every convention - Make the MINIMUM changes needed — no drive-by refactors
- No unrelated formatting changes, no renaming things "while you're in there"
- Each file you touch should be directly related to the PR description
- Run tests:
cargo test 2>/dev/null || npm test 2>/dev/null || pytest 2>/dev/null
Step 4: Self-review before simplifying
Check your own work:
git diff— read every line you changed- Are there files that shouldn't be in this PR? Revert them.
- Are there debug prints, TODO comments, or commented-out code? Remove them.
Step 5: Simplify
Launch a code-simplifier agent (sonnet) on the changed files:
- Remove unnecessary complexity, verbose error handling, over-abstraction
- Keep all functionality intact
- Make sure the code matches the project's existing style, not "AI style"
Step 6: Final review
Launch a code-reviewer agent (haiku) on the diff:
- Check for bugs, logic errors, security issues
- Check conventions match
.claude/rules/coding.md - Only flag HIGH confidence issues
Step 7: Commit and push
git add -A
git commit -m "feat: $ARGUMENTS"
git push origin HEAD
Step 8: Create PR
Use gh pr create with:
- Short title (under 70 chars)
- Body with: what changed, why, how to test
- Tag the PR for review
gh pr create --title "feat: $ARGUMENTS" --body "$(cat <<'EOF'
## What
[1-2 sentences: what this PR does]
## Why
[1 sentence: why this change is needed]
## Changes
- [bullet list of files/components changed]
## How to test
- [ ] [step-by-step testing checklist]
Co-Authored-By: Claude Opus 4.6 <[email protected]>
EOF
)"
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.
- 6d ago First seen · 109 lines · 14 tokens per session scan A a4a72e23901b
pr is a command published in the GitHub repository ScientiaCapital/unsloth-mcp-server (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 734 once invoked, about $0.0001 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-31.
Other commands, from other repositories
review-diff
Review the current working diff for correctness, security, and reuse.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
fix-comments
Address PR review comments by implementing requested changes automatically.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.