How do I put the critique loop in my agent's standing instructions?

Put the loop in the file your agent reads on every task. Then nobody has to remember to ask for the check, and every agent follows the same steps. Five lines are enough.

1. Find the file your agent reads

Each client’s connect page says where its file lives. The agent needs to be connected to the Vindex MCP server first.

2. Add the instruction

## Before you send or save customer-facing text
1. Use this rule set for this kind of output: <rule set name>.
2. Check the finished text with the Vindex validate tool. Send the whole text
   every time. Use one session_id for the whole task, and send agent_model.
3. If a rule fails, read that rule, fix the text against it, then run
   validate again. Do not resend text that has not changed.
4. Stop when every rule passes, when you reach the attempt limit, or when
   credits run out. Then tell the user which rule, if any, is still failing,
   and show the last draft.
5. Never say text was checked unless validate returned a result for it.

3. Make it yours

• One rule set for each kind of output. Name the right one for emails, for release notes, for documentation. An agent should choose the rule set written for the kind of output it is producing.
• What it does when it stops. The text above tells the agent to report and show the last draft. You may want it to ask a named person, or to open a ticket.
• What it does when credits run out. The refusal tells the agent the balance and who your Company admins are. Decide whether the agent should stop or carry on and flag the output as unchecked.

4. Confirm it fires

Hand the agent a task where you know the first draft breaks a rule. It should check, read the rule that failed, revise, check again, and tell you how it went. The result guide shows what each step returns.