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 komunite/tezgah --skill saas-testinggit clone --depth 1 https://github.com/komunite/tezgahWrote 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/komunite/tezgah/saas-testing)<a href="https://agentmods.dev/skills/komunite/tezgah/saas-testing"><img src="https://agentmods.dev/badge/skills/komunite/tezgah/saas-testing.svg" alt="Measured on agentmods" 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.00115 | $0.02291 |
| Opus 5 | $0.00057 | $0.01145 |
| Sonnet 5 | $0.00023 | $0.00458 |
| Haiku 4.5 | $0.00012 | $0.00229 |
Grade A, and why
saas-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 8d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SaaS Testing — Test Stratejisi ve Kalite Güvencesi
Bu skill, bir SaaS uygulamasının test altyapısını kurar. Test olmadan "production-ready" iddiası eksiktir — ödeme webhook'unun çalıştığını, auth akışının kırılmadığını ve API'nin beklendiği gibi davrandığını sadece testlerle garanti edebilirsin.
Bağımlılık: Bu skill saas-launcher orkestratör skill'inin Deployment öncesi kalite güvence adımıdır. Bağımsız olarak da kullanılabilir.
Bağlı skill'ler:
- saas-auth — Giriş/kayıt akışları E2E test edilir.
- saas-payments — Webhook handler'lar ve checkout akışı test edilir.
- saas-api-security — Rate limiting ve input validation testleri.
Test Piramidi — SaaS İçin
Hangi Test Türü Ne Zaman
Birim Test (Unit Test) — Vitest: Tekil fonksiyonları ve utility'leri test eder. Hızlı çalışır, dış bağımlılık yok. Kullanım: fiyat hesaplama, plan kontrolü, input validation, helper fonksiyonlar.
Entegrasyon Test (Integration Test) — Vitest: API route'larını test eder. HTTP isteği gönderir, yanıtı doğrular. Kullanım: auth endpoint'leri, checkout API, webhook handler.
Uçtan Uca Test (E2E Test) — Playwright: Gerçek bir tarayıcıda kullanıcı akışlarını test eder. En yavaş ama en güvenilir. Kullanım: kayıt → giriş → plan satın al → dashboard erişimi.
Başlangıç Önceliği
Day 1'de her şeyi test etmeye çalışma. Öncelik sırası:
- Webhook handler testi — Para alınıp plan aktifleşmezse gelir kaybı
- Auth akışı E2E testi — Giriş yapılamazsa uygulama kullanılamaz
- Kritik API route testleri — Plan kontrolü, kaynak oluşturma
- Input validation testleri — Güvenlik katmanı
Vitest Kurulumu
Neden Vitest
Jest'e alternatif, modern test runner. Avantajları: Vite tabanlı — çok hızlı, ESM desteği doğal, Jest uyumlu API (geçiş kolay), TypeScript desteği dahili, HMR ile watch mode.
Kurulum
npm install -D vitest @vitejs/plugin-react
Proje kökünde vitest.config.ts oluştur. Test dosyaları için __tests__/ klasörü veya dosya adında .test.ts / .spec.ts uzantısı kullan.
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.
- 8d ago First seen · 192 lines · 115 tokens per session scan A fef731d63ece
saas-testing is a skill published in the GitHub repository komunite/tezgah (90 stars, last pushed 5mo ago), licensed MIT. It adds 115 tokens to every session and 2,291 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
qa
A testing guide for checking software at three levels: small unit tests, tests of connected parts, and full end-to-end tests that mimic real use.
test-sweep
Run all test suites (unit, integration, API, E2E) and aggregate results into a summary report. Use after completing execution slices or before the Review Gate.
Test Generator
Skill "Test Generator" from databayt/hogwarts, covering test generation skill, test types, coverage and checklist.
nextjs-testing
Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects. Use when testing components with RTL, mocking APIs with MSW, or creating Playwright user flow tests.
testing-conventions
Testing conventions covering unit tests, component tests, and E2E tests. Auto-triggers when writing or modifying test files. Uses Vitest for unit/component tests and Playwright for E2E tests.