# Audit your bot instructions every week

> Tested by AI Setups That Work. Work · Intermediate · Life admin. Updated 2026-10-29.
> Receipt: Ran on Grok Bot, Oct 30, 2026, without the template: made-up 3-Bot fleet audited, all 3 planted slips caught with both wordings. Bot interviews were simulated.

Canonical page: https://www.aisetupsthatwork.com/setups/audit-bot-instructions-weekly-with-librarian-bot/

## What it does
Keep a fleet of bots honest about what they were told, with a weekly check that flags instructions that slipped or conflict.

## Who it's for
For anyone running more than a couple of bots who has noticed an old instruction quietly changing how a bot behaves.

## Tools
- The Librarian Bot template by Brian Roemmele, added from the public directory
- A list of the bots you actually run, so the audit covers all of them
- One place to keep the audit notes, so last week can be compared with this week

## Steps
1. Add the Librarian Bot template and point it at the bots you run.
2. Run the weekly interview: for each bot, ask what standing instructions it is following, in its own words.
3. Compare the answers with the instructions you actually gave. Flag anything that slipped, changed, or conflicts with another instruction.
4. Fix the flagged instructions at the source, in the bot itself, not only in the audit note.
5. Keep the audit notes week to week, so a slow drift shows up as a trend instead of a surprise.

## Copy-paste prompt
Adapt bracketed fields to your situation.
```text
Interview each bot I run, one at a time, and list the standing instructions it is following, in its own words. Compare them with the instructions I gave, and flag any instruction that slipped, changed, or conflicts with another instruction. Do not change any bot instruction yourself. Report the flags and the exact wording on both sides, so I can fix them at the source.
```

## Guardrails
- What it touches: Connected mail, calendar, sheets, or chat. Scoped to this job (The Librarian Bot template by Brian Roemmele, added from the public directory; A list of the bots you actually run, so the audit covers all of them).
- Needs your OK: Send, pay, publish, and account changes stay with you. Treat agent output as drafts first.
- Safety level: Read-only
- An audit that only checks one bot while the rest drift unnoticed; cover the whole fleet.
- A flagged instruction fixed in the note but not in the bot, so it slips again next week.
- An interview that paraphrases instead of quoting; ask for the wording as the bot holds it.

## Tips
- Run the audit on a schedule, not when something already broke.
- Fix at the source. An audit note alone does not change a bot.
- Watch for conflicts, not just drift. Two instructions can both be remembered and still disagree.

## Estimates (labeled, not measured)
- Time saved: Not measured yet.
- Money saved: Not stated in sources.
- Tool cost: Template is free to add. Check your bot plan for usage limits.

## Sources
Summaries use the public sources below, not independent verification.
- Brian Roemmele, GrokBot.Rocks directory: https://grokbot.rocks (Directory checked 2026-10-29: updated October 28, 2026, tracking 7,539 public bot templates in 26 categories, refreshed every week. Its Librarian Bot entry by Brian Roemmele says: your bots forget what you told them weeks ago, and Librarian interviews your bots every week, finds the standing instructions you gave them, and flags the ones that are slipping.)

## Get the free starter pack
Five beginner copy-paste AI setups, free by email: https://www.aisetupsthatwork.com/starter-pack/?utm_source=ai-agent&utm_medium=markdown&utm_campaign=setup-audit-bot-instructions-weekly-with-librarian-bot

Related:
- [AI chief of staff bot](https://www.aisetupsthatwork.com/setups/ai-chief-of-staff-bot/index.md)
- [How to give your AI bot a long-term memory with an Obsidian vault](https://www.aisetupsthatwork.com/setups/give-your-ai-bot-a-long-term-memory-with-obsidian/index.md)