Back to Prompt Library
testing

Testing and Optimization with Adaptive Budgets

Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.

Linked challenge: Real-time Cyber Incident Response

Format
Text-first
Lines
1
Sections
1
Linked challenge
Real-time Cyber Incident Response

Prompt source

Original prompt text with formatting preserved for inspection.

1 lines
1 sections
No variables
0 checklist items
Simulate several DDoS scenarios (SYN flood, UDP flood, HTTP flood) with varying severity and test your agent system. Monitor its detection latency, mitigation accuracy, and LLM token usage. Implement and refine adaptive thinking budgets, where higher-severity incidents trigger more extensive LLM calls (e.g., multi-turn reasoning with Claude Opus 4.1) while lower-severity events use more concise, rapid reasoning from Gemini 2.5 Pro or cached knowledge. Document your findings and improvements.

Adaptation plan

Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.

Keep stable

Preserve the rubric, target behavior, and pass-fail criteria as the baseline for evaluation.

Tune next

Adjust fixtures, mocks, and thresholds to the system under test instead of weakening the assertions.

Verify after

Make sure the prompt catches regressions instead of just mirroring the happy-path examples.