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 fix-issuegit 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/fix-issue)<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/fix-issue"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/fix-issue/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/fix-issue"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/fix-issue.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.00290 |
| Opus 5.5 | $0.00008 | $0.00116 |
| Sonnet 5.5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
fix-issue 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
GitHub issue #$1 için aşağıdaki adımları takip et:
1. Issue'yu Oku
gh issue view $1
2. Analiz Et
- Issue'nun tam olarak ne istediğini anla
- İlgili dosyaları ve kod bölgelerini tespit et
- Varsa bağlantılı issue'ları veya PR'ları kontrol et:
gh issue view $1 --comments
3. Çözümü Uygula
- Minimal değişiklik yap - sadece issue'nun gerektirdiklerini
- Mevcut kod stiline uy
- Gerekirse test ekle veya güncelle
4. Doğrula
- Değişiklikleri gözden geçir
- Testleri çalıştır
5. Commit Hazırla
git add -p
Commit mesajı şu formatta olsun:
fix: <issue başlığından kısa özet>
Closes #$1
Issue'yu kapat ve çözümü özetle.
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 · 43 lines · 21 tokens per session scan A 1ee3e07845fe
fix-issue is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (11 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 290 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
generate-rfcs
Break the PRD into sequenced implementation RFCs under RFCs/ with an RFCS.md index, then cold-read each RFC for gaps.
workflow-status
Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.