Stress test
A ruthlessly strict algorithmic optimization methodology for AI coding agents. Forces your agent to profile, benchmark, and mathematically prove performance gains before writing code.
npx -y skills add v0idOS/performance-deity --skill stress-testAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Stress test and harden code against extreme inputs, malformed data, and simulated infrastructure failures. Acts as a red team. Documents every crash, then hardens the boundary.
SKILL.md
1.5 KB, as published. Nobody here has run it
Execute all four phases in order.
Phase 1 — Fuzzer
Write a script that sends the following inputs to the target function:
- 1GB string payloads
null,undefined,NaN,-1,Infinity- Deeply nested recursive JSON (depth >1,000)
- Malformed Unicode strings (
\uFFFD, null bytes, RTL override characters) - Simulated network drops or database timeouts via mocked I/O
Phase 2 — Attack
Run the fuzzer. For each failure, document:
- The exact input that caused the failure
- The failure mode: unhandled exception, memory exhaustion, infinite loop, or incorrect output without error
Phase 3 — Hardening
For every documented failure:
- Add input validation at the function boundary. Reject invalid input immediately with a typed error.
- Add pagination or streaming for inputs that exceed a byte threshold.
- Add a circuit breaker or retry-with-exponential-backoff for every network and database dependency.
Phase 4 — Report
Re-run the full fuzzer. For every input that previously caused a crash, show the new response.
| Input | Before | After |
|---|---|---|
| 1GB string | Crash / OOM | 400 Bad Request |
| Null input | Unhandled exception | Typed error returned |
| Nested JSON 1k deep | Stack overflow | Rejected at boundary |
Zero crashes is the target.