# Review
用 Promptfoo 做提示词与模型评测:文档核验版上手指南
文档核验版上手指南:在 Node.js 22.22.0 或更新版本上,按官方文档用 init --example get...

After the MiniMax M3 weights are open-sourced: Should the encoding agent be switched immediately?
Focusing on the MiniMax M3 open-source weights: a three-way comparison of the flagship closed-source model vs. the M3 API/weights service, examining long-position completion rates, unit cost, multimodal capabilities, and more...

Should batch Agent tasks be immediately switched to a cheaper computer-use tier?
Comparison of GPT-6.1 Terra Public Pricing: Flagship Tier vs. Budget "Computer-Use" Tier in Terms of Completion Rate, Cost Per Task, Failure Rate...

When an agent fails, it's usually not because the tools aren't sufficient, but because the scope of its actions wasn't clearly defined.
Comparison: Clearly Defined Boundaries vs. Heap Tools. Success rate does not equate to safe boundaries; write the envelope tonight and retest using out-of-bounds use cases.

Multi-agent systems seem exciting, but I’d rather start by clearly defining the scope of a single-agent tool first.
The "Three-Piece Set" for Aggregating Executable Boundaries: Tool Table, Confirmation Gate, and Prohibited Use Cases; can be submitted tonight—no empty talk about multiple agents.
