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 berkcangumusisik/claude-code-practices --skill pr-reviewgit clone --depth 1 https://github.com/berkcangumusisik/claude-code-practicesWrote 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/berkcangumusisik/claude-code-practices/pr-review)<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/pr-review"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/pr-review/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/berkcangumusisik/claude-code-practices/pr-review"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/pr-review.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.00021 | $0.00469 |
| Opus 5 | $0.00010 | $0.00234 |
| Sonnet 5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
pr-review 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 9d 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.
What it actually says
PR Bağlamı
Diff:
!`gh pr diff $1 2>/dev/null || gh pr diff`
Açıklama ve yorumlar:
!`gh pr view $1 --comments 2>/dev/null || gh pr view --comments`
CI durumu:
!`gh pr checks $1 2>/dev/null || gh pr checks`
İnceleme Kriterleri
Aşağıdaki alanlarda kapsamlı inceleme yap:
Doğruluk
- Değişiklikler PR açıklamasındaki amacı karşılıyor mu?
- Edge case'ler ele alınmış mı?
- Hata yönetimi yeterli mi?
Güvenlik
- SQL injection, XSS, CSRF gibi açıklar var mı?
- Hassas veriler loglanıyor veya expose ediliyor mu?
- Yetkilendirme kontrolleri doğru mu?
Kod Kalitesi
- Kod DRY prensiplerine uyuyor mu?
- Fonksiyonlar tek sorumluluk ilkesini takip ediyor mu?
- Karmaşık mantık için yeterli yorum var mı?
Test
- Yeni kod için test yazılmış mı?
- Mevcut testler hâlâ geçiyor mu?
- Test senaryoları yeterli kapsamı sağlıyor mu?
Performans
- Gereksiz veritabanı sorgusu veya API çağrısı var mı?
- Büyük veri setleri için düşünülmüş mü?
Çıktı Formatı
Şu başlıklar altında bulgularını sun:
Kritik Sorunlar - merge öncesi mutlaka düzeltilmeli
Öneriler - kaliteyi artıracak değişiklikler
Küçük Notlar - stil veya tercih meselesi
Olumlu Noktalar - iyi yapılan şeyler
Her bulgu için ilgili dosya ve satır numarasını belirt.
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.
- 9d ago First seen · 69 lines · 21 tokens per session scan A 1c7ae7c387df
pr-review is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (10 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 469 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 skills, from other repositories
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
generic-react-code-reviewer
Review React/TypeScript code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Enforces TypeScript strict mode, GPU-accelerated animations, WCAG AA accessibility, bundle size limits, and surgical simplicity. Use when completing features, before commits, or…
generic-fullstack-code-reviewer
Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.
generic-static-code-reviewer
Review static site code for bugs, security issues, performance problems, accessibility gaps, and CLAUDE.md compliance. Enforces pure HTML/CSS/JS standards, minimal page weight, mobile-first design. Use when completing features, before commits, or reviewing changes.