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 omergocmen/vibe-coder-kit --skill githubgit clone --depth 1 https://github.com/omergocmen/vibe-coder-kitWrote 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/omergocmen/vibe-coder-kit/github)<a href="https://agentmods.dev/skills/omergocmen/vibe-coder-kit/github"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/github/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/omergocmen/vibe-coder-kit/github"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/github.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.00060 | $0.02093 |
| Opus 5.5 | $0.00024 | $0.00837 |
| Sonnet 5.5 | $0.00012 | $0.00419 |
| Haiku 4.5 | $0.00006 | $0.00209 |
Grade A, and why
github 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Skill
Temel Kural
Hiçbir commit code-review skill çalıştırılmadan atılmaz.
Bu kural ihlal edilemez. "Küçük değişiklik" veya "sadece bir satır" istisnası yoktur.
Commit Standardı — Conventional Commits
Format
<type>(<scope>): <subject>
[body — opsiyonel]
[footer — opsiyonel]
Type Listesi
| Type | Ne Zaman Kullanılır |
|---|---|
feat |
Yeni özellik |
fix |
Bug düzeltmesi |
refactor |
Davranış değişmeden kod düzenlemesi |
style |
Formatlama, boşluk (işlevsel değişiklik yok) |
test |
Test ekleme veya düzenleme |
docs |
Dokümantasyon değişikliği |
chore |
Build, dependency, config güncellemesi |
perf |
Performans iyileştirmesi |
ci |
CI/CD pipeline değişikliği |
revert |
Önceki commit'i geri alma |
Scope (Opsiyonel ama Önerilir)
Etkilenen modül, komponent veya katman:
feat(auth): add refresh token rotation
fix(userService): handle null email in validation
refactor(Button): extract loading state to hook
chore(deps): upgrade react to 19.2.0
Subject Kuralları
- İmperative mood kullan (Türkçe: emir kipi): "add" not "added", "fix" not "fixed"
- Küçük harf ile başla
- Nokta ile bitirme
- 72 karakter sınırı
- Ne değiştiğini yaz, neden body'de açıkla
Body (Neden Değişti?)
feat(auth): add refresh token rotation
Statik refresh token'lar çalınırsa süresiz erişim sağlar.
Rotation ile her kullanımda yeni token üretilir, eskisi geçersiz kılınır.
RFC 6749 güvenlik önerisi doğrultusunda implement edildi.
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 · 292 lines · 60 tokens per session scan A c57d48cefaf3
github is a skill published in the GitHub repository omergocmen/vibe-coder-kit (94 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 2,093 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.
git-pr-workflows-pr-enhance
Improve pull request descriptions, change summaries, validation details, and review workflows. Use when preparing a pull request or making an existing proposal easier to evaluate.
pr-workflow
Pull request lifecycle: commit, codex review, sync, review, fix, status, cleanup, and PR mining. Use when user wants to commit changes, get a second-opinion code review from Codex, push changes, create a PR, check PR status, fix review comments, clean up branches after merge, or mine tribal knowledge from PR reviews.…
pr-review
Review pull requests and Git diffs with Graph-It-Live risk, breaking-change, dependency-impact, cycle, unused-export, and test-candidate evidence. Use when asked to review a PR, inspect a diff, assess merge risk, check a branch before merging, create a Graph-It-Live review gate, or explain review-pr results. Trigger…
pr
Pull request excellence and review optimization.
github-pr-best-practices
Best practices for creating GitHub pull requests including conventional commits, PR formatting, and multi-language support (en/ja). Use when creating PRs, writing PR descriptions, or formatting commit messages.