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 test-runnergit 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/test-runner)<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/test-runner"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/test-runner/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/test-runner"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/test-runner.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.00023 | $0.00358 |
| Opus 5 | $0.00012 | $0.00179 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
test-runner 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 6d 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
Testleri Çalıştır
Önce mevcut test komutunu tespit et:
package.jsoniçindekitestscriptini oku- Varsa test framework'ü belirle (Jest, Vitest, Mocha vb.)
Testleri çalıştır (pattern belirtilmişse: $1):
# Pattern varsa / If pattern provided: $1
Sonuçları Analiz Et
Başarısız Testler
Her başarısız test için:
- Hata mesajını oku
- İlgili kaynak dosyayı ve test dosyasını incele
- Hatanın kaynağını tespit et:
- Kod değişikliğinden mi kaynaklanıyor?
- Test ortamı sorunu mu?
- Beklenti (assertion) yanlış mı?
Kök Neden Analizi
- Birden fazla test aynı sebepten mi başarısız?
- Ortak bir pattern var mı?
Düzeltme Öner
Her başarısız test için:
- Sorunu açıkla
- Olası düzeltmeyi göster
- Düzeltmeyi uygulamamı ister misin? diye sor
Özet Rapor
Toplam: X test
Geçti: Y ✓
Kaldı: Z ✗
Kök nedenler:
1. ...
2. ...
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.
- 6d ago First seen · 54 lines · 23 tokens per session scan A 6fd24c505279
test-runner is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (10 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 358 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-09-03.
Other skills, from other repositories
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
code-review
Reviews code for bugs, security issues, and best practices.
paired-probe
Refuse a verdict a probe did not earn. Runs a check where the fault IS present and where it is NOT, and blocks the answer when both arms print the same thing, because a check that cannot disagree with you has measured nothing. Also catches the zero-sample sweep that reads as "clean" and the swallowed error that reads…
bug-reproducer
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix. Also turn bug reports, stack traces, screenshots, failing behavior, support tickets, and regressions into minimal reproducible cases with red-to-green evidence. Use when…
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.