Borrowing it
Nothing to install: this file belongs to AI-agents-incubator/n8n-pilot. 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/AI-agents-incubator/n8n-pilot/main/.claude/commands/pr.mdgit clone --depth 1 https://github.com/AI-agents-incubator/n8n-pilotWrote 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/ai-agents-incubator/n8n-pilot/pr)<a href="https://agentmods.dev/commands/ai-agents-incubator/n8n-pilot/pr"><img src="https://agentmods.dev/badge/commands/ai-agents-incubator/n8n-pilot/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/commands/ai-agents-incubator/n8n-pilot/pr"><img src="https://agentmods.dev/badge/commands/ai-agents-incubator/n8n-pilot/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.00009 | $0.01762 |
| Opus 5 | $0.00005 | $0.00881 |
| Sonnet 5 | $0.00002 | $0.00352 |
| Haiku 4.5 | $0.00001 | $0.00176 |
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 4d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Создай Pull Request используя GitHub CLI (gh).
ВАЖНО: Анализируй ВСЕ коммиты, не только последний!
Процесс:
1. Анализ текущего состояния ветки
Выполни параллельно эти команды:
# Проверь текущую ветку и статус
git status
# Посмотри unstaged и staged изменения
git diff
git diff --staged
# Проверь remote tracking
git branch -vv
# Посмотри ВСЕ коммиты от base branch (обычно main)
git log main..HEAD --oneline
# Посмотри полный diff от base branch
git diff main...HEAD --stat
2. Определи base branch
Обычно это main или master. Проверь:
git remote show origin | grep "HEAD branch"
3. Анализируй ВСЕ изменения
КРИТИЧНО: Не смотри только последний коммит! Проанализируй:
- Все коммиты с момента divergence от main
- Весь diff между base branch и HEAD
- Все измененные файлы
# Полный список измененных файлов
git diff main...HEAD --name-status
# Детальный diff всех изменений
git diff main...HEAD
4. Составь PR описание
Формат:
## Summary
[1-3 bullet points описывающие ЧТО было сделано]
## Why (Мотивация)
[ПОЧЕМУ эти изменения необходимы - бизнес-контекст]
## What Changed
[Детальное описание изменений по категориям]
### Added
- [Новая функциональность]
### Changed
- [Изменения в существующей функциональности]
### Fixed
- [Исправленные баги]
### Security
- [Изменения связанные с безопасностью]
## Technical Details
[Технические детали для ревьюеров]
- Архитектурные решения
- Важные изменения в API/схеме БД
- Performance implications
## Test Plan
- [ ] Unit tests pass (`make test`)
- [ ] Type checking pass (`make typecheck`)
- [ ] Linting pass (`make lint`)
- [ ] Manual testing: [опиши что протестировал]
- [ ] Security check (`make security`)
- [ ] Tested edge cases: [какие]
## Screenshots/Demo
[Если есть UI изменения - добавь скриншоты]
## Breaking Changes
[Если есть breaking changes - опиши их здесь]
- [ ] Documentation updated
- [ ] Migration guide provided
## Checklist
- [ ] Code follows project style guide
- [ ] Documentation updated (README, ARCHITECTURE, etc.)
- [ ] BACKLOG.md updated with implementation status
- [ ] Security best practices followed (see SECURITY.md)
- [ ] No secrets in code
- [ ] All tests passing
🤖 Generated with [Claude Code](https://claude.com/claude-code)
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.
- 4d ago First seen · 274 lines · 9 tokens per session scan A f2135592460a
pr is a command published in the GitHub repository AI-agents-incubator/n8n-pilot (29 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,762 once invoked, about $0.0000 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-09-04.
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.