runaway-guard
Implements cost-safety measures for AI APIs, ensuring strict budget controls to prevent unexpected expenses during execution.
Install this skill
Security score
The runaway-guard skill was audited on Jun 1, 2026 and we found 13 security issues across 3 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Template literal with variable interpolation in command context
| 163 | // idempotency: key = `${campaignId}:${sha1(prompt)}` — provider-side dedup window 24h |
Template literal with variable interpolation in command context
| 178 | `prompt count ${prompts.length} exceeds MAX_IMAGES_PER_RUN=${MAX_IMAGES_PER_RUN}` |
Template literal with variable interpolation in command context
| 182 | `img:${event.data.id}:${sha1(p)}`, // idempotency key |
Webhook reference - potential data exfiltration
| 18 | Every loop has time complexity and space complexity. A loop that calls a paid API has a third: **dollars per execution**. The model tracks the first two automatically. It does not track the third, so |
Webhook reference - potential data exfiltration
| 30 | - Writing or reviewing code that calls a paid AI / inference API in a loop, queue, retry path, agent step, webhook handler, or background job. |
Webhook reference - potential data exfiltration
| 96 | 6. **Idempotency keys on every mutating or charging call.** A webhook that fires twice should bill once. Without an idempotency key, retry policies you cannot see (load balancer, framework, gateway) s |
Webhook reference - potential data exfiltration
| 100 | - **Webhook handlers that call the API that called the webhook.** Cycle detection or it will cycle. |
Webhook reference - potential data exfiltration
| 199 | | Webhook handler → API call | idempotency key required; cycle if webhook is triggered by the same API | provider rate limit per key | |
Webhook reference - potential data exfiltration
| 212 | - Webhooks: deliveries are paid; cap retries on your side. |
Webhook reference - potential data exfiltration
| 253 | | Webhook retried by provider | idempotency at the handler boundary | |
Webhook reference - potential data exfiltration
| 285 | | "Idempotency is overkill for this." | Webhooks retry. Load balancers retry. Browsers retry. Without an idempotency key, *something* will duplicate. | |
Webhook reference - potential data exfiltration
| 299 | - About to handle a webhook that calls the API that produced the webhook. |
Access to .env file
| 298 | - About to commit a paid API key to a `.env` shared across environments. |