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 fthsrbst/mnema --skill testinggit clone --depth 1 https://github.com/fthsrbst/mnemaWrote 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/fthsrbst/mnema/testing)<a href="https://agentmods.dev/skills/fthsrbst/mnema/testing"><img src="https://agentmods.dev/badge/skills/fthsrbst/mnema/testing/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/fthsrbst/mnema/testing"><img src="https://agentmods.dev/badge/skills/fthsrbst/mnema/testing.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.00059 | $0.00565 |
| Opus 5.5 | $0.00024 | $0.00226 |
| Sonnet 5.5 | $0.00012 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
testing 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
Testing — Ne Zaman, Ne Kadar, Nasıl
Temel kurallar
- Her bug düzeltmesi = önce onu yakalayan test. Test kırmızıyken düzelt, yeşile dön (bu repo'daki smoke pattern'i). Testsiz düzeltilen bug geri gelir.
- Davranışı test et, implementasyonu değil: "fonksiyon X'i çağırıyor mu" değil, "girdi A → çıktı B mi". İç yapıya bağlı test, her refactor'da kırılan yüktür.
- Test piramidi pragmatik: Bol hızlı birim testi çekirdek mantığa (chunker, arama, LWW merge gibi); az sayıda uçtan uca smoke gerçek akışa (kaydet→ara→bul). UI/entegrasyon testini gerçek fayda varsa yaz.
Neyi MUTLAKA test et
- Para/veri kaybettirebilecek yollar: silme, senkron/merge, migration
- Sınır koşulları: boş, null, unicode/Türkçe, eşzamanlılık, büyük girdi
- Sözleşmeler: API response şekli, geriye dönük uyumluluk
- Daha önce kırılmış her şey (regresyon)
Neyi test ETME
- Framework'ün kendisini (express route'a istek atıp "çalışıyor mu" bakmak — bir smoke yeter)
- Getter/setter, saf konfig, tek satırlık delegasyon
- Mock'un mock'unu gerektiren şeyler — tasarım kokusudur; önce bağımlılığı ayrıştır
Pratik akış (yeni özellik)
- En riskli davranışı belirle → onun testini İLK yaz (kırmızı)
- Geçir (yeşil), sonra kenar durumları ekle
- Smoke'a bir uçtan uca satır ekle (gerçek akış hâlâ bütün mü?)
- CI yoksa bile:
npm run smokealışkanlığı — commit'ten önce çalıştır
Hata anatomisi
Test başarısız olduğunda mesaj üç soruyu cevaplamalı: ne bekleniyordu, ne geldi, hangi girdiyle. assert(x) değil assert.equal(sonuc, beklenen, "girdi: ...").
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 · 32 lines · 59 tokens per session scan A f1f3cd689070
testing is a skill published in the GitHub repository fthsrbst/mnema (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 565 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-31.
Other skills, from other repositories
knowledge-engineering-quality-and-delivery-unit-integration-and-shared-test-harnesses
A testing guide for the CLI and web interfaces, covering unit, integration, end-to-end, and real-process test setup with shared fixtures and cleanup.
Jest Test Framework
Execute and generate Jest tests for JavaScript/TypeScript projects with support for unit, integration, and E2E testing.
test-writing
Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.
testing-strategy
Test selection and scope guidance: tiers, marks, batching, cross-module regressions. Loaded by the testing rule module. Triggers: 'which tests should I run', 'test scope', 'test tiers'. NOT for: writing tests (use test-driven-development) or fixing broken tests (use fixing-tests).
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
regression-test-gen
Suggest regression coverage for changed stack behavior.