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-api-securitygit 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-api-security)<a href="https://agentmods.dev/skills/komunite/tezgah/saas-api-security"><img src="https://agentmods.dev/badge/skills/komunite/tezgah/saas-api-security.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.00108 | $0.03061 |
| Opus 5 | $0.00054 | $0.01530 |
| Sonnet 5 | $0.00022 | $0.00612 |
| Haiku 4.5 | $0.00011 | $0.00306 |
Grade A, and why
saas-api-security 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SaaS API Security — Güvenlik ve Kalite Katmanı
Bu skill, bir SaaS uygulamasının API katmanını güvenlik, dayanıklılık ve kalite açısından sağlamlaştırır. Diğer katmanların (auth, payments) üzerine son bir koruma ve kalite katmanı olarak eklenir.
Bağımlılık: Bu skill saas-launcher orkestratör skill'inin Faz 7'sidir. Bağımsız olarak da kullanılabilir.
Bağlı skill'ler:
- saas-auth — Oturum bilgisi API korumasının temelini oluşturur.
- saas-payments — Plan bilgisi erişim kontrolü kararlarını belirler.
Güvenlik Katmanları Mimarisi
Bir API isteği geldğinde sırasıyla şu katmanlardan geçmelidir:
İstek geldi
→ 1. Rate Limiting (çok fazla istek mi?)
→ 2. Authentication (kim bu?)
→ 3. Authorization (bu işlemi yapma yetkisi var mı? Planı uygun mu?)
→ 4. Input Validation (gönderdiği veri geçerli mi?)
→ 5. İş Mantığı (asıl işlem)
→ 6. Hata Yönetimi (bir şeyler ters giderse)
→ Cevap döndür
Her katman bağımsızdır ve ihlal durumunda sonraki katmanlara geçmeden isteği reddeder.
1. Rate Limiting
Neden Gerekli
Rate limiting olmadan:
- Bir kullanıcı (veya bot) saniyede binlerce istek göndererek sunucunu çökertebilir (DDoS)
- Brute force saldırıları giriş sayfasını hedef alabilir
- API'ni bedava kullanan biri kaynaklarını tüketebilir
- Ödeme webhook endpoint'in dışarıdan spam'lanabilir
Strateji
Rate limit'i iki seviyede uygula:
Global seviye (IP bazlı): Tüm endpoint'lere uygula. Saniyede veya dakikada belirli sayıda istek. Amaç: DDoS ve brute force koruması.
Endpoint seviyesi (kullanıcı bazlı): Hassas endpoint'lere ayrıca uygula — login denemesi, checkout oluşturma, e-posta gönderimi. Amaç: kaynakların adil kullanımı.
Serverless Ortamda Rate Limiting
Serverless ortamlarda (Vercel, Netlify) her istek ayrı bir process'te çalışır. Bu yüzden in-memory rate limiting (bellekte sayaç tutma) çalışmaz — her process kendi belleğine sahiptir, sayaçlar paylaşılmaz.
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 · 256 lines · 108 tokens per session scan A c07d0d90c90c
saas-api-security is a skill published in the GitHub repository komunite/tezgah (90 stars, last pushed 5mo ago), licensed MIT. It adds 108 tokens to every session and 3,061 once invoked, about $0.0005 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
API Designer
Skill "API Designer" from databayt/hogwarts, covering api design skill, server action pattern and checklist.
Multi-Tenant Validator
Skill "Multi-Tenant Validator" from databayt/hogwarts, covering multi-tenant safety skill, rules and checklist.
nextjs-app-router
Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
links
Configure the tRPC client link chain: httpLink, httpBatchLink, httpBatchStreamLink, splitLink, loggerLink, wsLink, createWSClient, httpSubscriptionLink, unstablelocalLink, retryLink. Choose the right terminating link. Route subscriptions via splitLink. Build custom links for SOA routing. Link options: url, headers…