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 commitgit 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/commit)<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/commit"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/commit/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/commit"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/commit.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.00019 | $0.00335 |
| Opus 5.5 | $0.00008 | $0.00134 |
| Sonnet 5.5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
commit 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.
What it actually says
Değişiklikleri İncele
git diff --staged
git status
git log --oneline -5
Commit Mesajı Oluştur
Conventional Commits formatını kullan:
<type>(<scope>): <kısa açıklama>
[isteğe bağlı gövde]
[isteğe bağlı footer]
Type Seçimi
feat- yeni özellikfix- hata düzeltmesirefactor- davranış değişikliği olmayan yeniden yapılandırmatest- test ekleme veya düzeltmedocs- yalnızca dokümantasyonstyle- biçimlendirme (logic yok)chore- build, bağımlılık güncellemesiperf- performans iyileştirmesici- CI/CD değişikliği
Kurallar
- Başlık satırı 72 karakteri geçmemeli
- Türkçe veya İngilizce - repo'daki mevcut dili kullan
- "ne yaptı" değil "ne yapar" odaklı: "Ekle" değil "Ekledi"
- Breaking change varsa footer'a
BREAKING CHANGE:ekle
Uygula
Onaylanan mesajla commit oluştur:
git commit -m "..."
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 · 52 lines · 19 tokens per session scan A 8a7deac3e45f
commit is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (11 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 335 once invoked, about $0.0001 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-31.
Other skills, from other repositories
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
commit
Create git commits with user approval and no Claude attribution.
shipit
Turn finished work into a clean commit and pull request. Always asks first whether the commit and PR should carry AI/bot authorship attribution or stay fully human-authored, then matches the repository's existing commit conventions, splits work into logical commits, and writes a PR body with context, risk, and…
commit
Smart commit with Ollama-generated messages. Conventional commits, auto-push option. Triggers on: commit this, commit changes, smart commit, /commit.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
commit-push-pr
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.