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.
git clone --depth 1 https://github.com/GktuOktay/ai-skillsWrote 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/rules/gktuoktay/ai-skills/pre-mortem-stress-test)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/pre-mortem-stress-test"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/pre-mortem-stress-test/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/rules/gktuoktay/ai-skills/pre-mortem-stress-test"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/pre-mortem-stress-test.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.00000 | $0.00460 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
pre-mortem-stress-test 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.
What it actually says
Pre-Mortem & System Stress Tester
Bu skill, büyük bir mimari değişiklik, yeni bir veritabanı veya kritik bir sistem bileşeni canlıya alınmadan önce çalışır. "Ön Otopsi" (Pre-Mortem) yöntemiyle sistemin gelecekte çökeceği senaryoyu simüle eder ve en zayıf halkanı tespit eder.
💥 Stres Testi Katmanları
- Yük ve Ölçeklenme Çöküşü (Traffic Spikes): Aniden 10x trafik gelirse sistem hangi noktada tıkanır? (Connection Pool, Rate Limit, CPU bottleneck).
- Bağımlılık İflası (Third-party Failure): Harici servis (Payment Gateway, Auth Provider, Mail API) 500 hatası verirse veya 5 saniye gecikirse sistem nasıl davranır?
- Veri Tutarsızlığı (Data Corruption): Veritabanı yazma anında sunucu kapanırsa veri tutarlı kalır mı? (Transaction rollback var mı?).
- Güvenlik & Yetkilendirme İhlali (Bypass): Saldırgan bu akışta yetki kontrolünü nasıl atlatabilir?
📊 Raporlama Formatı
💣 Sistem Ön Otopsi Raporu (Pre-Mortem Simulation)
- 💀 Muhtemel Çöküş Noktası #1:
[Senaryo ve Bileşen]- ⚠️ Zayıf Halka (Single Point of Failure):
[Neden patlar?]- 🛡️ Önleyici Savunma (Mitigation Plan):
[Nasıl engellenir?]
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 · 27 lines · 460 tokens per session scan A 86e2737b2988
pre-mortem-stress-test is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 460 tokens. 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 cursor rules, from other repositories
evaluation-protocol
Evaluation protocol for blind skill testing across model tiers.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.