Test Twilio Rate-Limit Handling with Codex
Review bounded retry and callback processing behavior with a fake Twilio response sequence and predetermined delays.
中文Setup for Codex (Twilio Developer Kit)
Use Codex in a scratch workspace. The exercise takes local mock data or a written scenario. Check provider prerequisites before running it against a test account.
- In Codex, open /plugins and install Twilio Developer Kit. To reproduce the exact revision, use the pinned Twilio source linked below and its Codex instructions in the repository README.
- Open the practice project, invoke $twilio-reliability-patterns and paste the example inputs. Use the installed package with its related skills and references.
Example task
Use $twilio-reliability-patterns and a local fake sender that returns 429, 429, then success. Set a three-attempt budget and inject waits of 100 and 200 milliseconds so the sequence is deterministic.Expected result
The client performs three calls, schedules exactly two waits, and stops after the success. A separate permanent failure fixture exits after one call.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Why inject delays in a retry test?
A fake clock keeps the test deterministic. Check the documented rate limit and configure production backoff and jitter separately.