← Back to library

Audit what your agent assumes about you, with evidence

Michael Fenech (@Michael_Fenech_) posted an Assumption Audit for the Chief of Staff Bot in Grok Bot. It makes the agent separate what you actually told it from what it guessed, show the source for each belief and ask you about the five riskiest ones before changing its memory. We show his prompt word for word with credit.

  • OutcomeAsk your agent to list the preferences, limits and past choices it uses to shape its work for you, label each as something you said, something it inferred or of unknown origin, show where it came from and what it could change, then bring you the five that matter most so you can confirm, correct, narrow or delete them before it edits anything.
  • SetupMinutes
  • LevelStarter
  • CreditMichael Fenech (@Michael_Fenech_)
View original
Works with
Grok BotChatGPTClaudeGemini

Published Nov 15, 2026Updated Nov 15, 2026AI dry run on sample input: passed Nov 15, 2026Source verified Nov 15, 2026

When should you use it?

  • Your agent's suggestions feel slightly off and you suspect an old preference is steering them
  • It has run for weeks with memory on and you have never reviewed what it kept
  • You shared an account or delegated work for someone else and want to check nothing leaked into your profile

Not for: Brand new assistants with no saved memory or history yet; Deleting memory in bulk; this is a review that waits for your answers; Tools that cannot show you their saved memories or instructions

What do you need, and what do you get?

You need

  • An agent with saved memories, instructions or chat history it can read
  • Ten to fifteen minutes to answer five questions

You get

  • A list of beliefs about you, each labeled as stated, inferred, task-specific or unknown origin
  • The wording and location behind each belief, or a note that it cannot be traced
  • How each uncertain belief could change the agent's work, marked as real or possible
  • Five priority questions, with nothing changed until you reply

How does it work, step by step?

  1. Pick the right agentRun it with the agent that sees the most of your work, such as a chief of staff or main assistant.
  2. Paste the promptUse Fenech's prompt as written. It tells the agent not to change anything during the review.
  3. Read what it could not inspectNote any memory or history it says it cannot open, so you know the audit is partial.
  4. Answer the five questionsFor each item, confirm it, correct it, limit it to one situation or person, or ask for it to be removed.
  5. Repeat after big changesRun it again after a new job, a move or a change in budget, when old preferences are most likely to be stale.

The prompt

The original prompt by Michael Fenech (@Michael_Fenech_), word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, ChatGPT, Claude and others. Values in lime are placeholders.

Original prompt by Michael Fenech (@Michael_Fenech_)

Word for wordby Michael Fenech (@Michael_Fenech_)
Run an Assumption Audit on what you know about me.

Review the memories, instructions and conversation history you can access. Tell me what you couldn’t inspect. Don’t change anything yet.

1 - Identify what you’re treating as true

Find the preferences, priorities, constraints and decisions about me that you use to shape recommendations or work.

Focus on things that could change the result: budget, quality, communication style, availability, goals and agreed plans.

2 - Separate facts from assumptions

For each item, classify it as explicitly stated by me, inferred by you, limited to a particular task or person, or source unknown.

Don’t treat something as confirmed just because it appears in a saved memory.

3 - Show the evidence

Show the relevant wording and where you found it. Include the original message or context if available.

If you can’t establish where something came from, say so. Don’t invent an explanation.

Check whether a request for someone else became a preference attributed to me, or an idea we discussed became a decision I supposedly made.

4 - Explain why it matters

For each uncertain item, explain how using it could affect your work.

Where you can identify a real example, show it. Otherwise, clearly label the impact as a possibility.

5 - Bring me the five most important checks

Prioritise uncertain assumptions with the biggest potential effect.

For each, show what you’re treating as true, the evidence, the possible consequence and one question for me to answer.

Let me confirm it, correct it, limit it to a specific context or ask you to remove it. Wait for my answers before making changes.

Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: an Assumption Audit for what Grok Bot believes about you.

Our adapted version (optional)

Fill in the blanks (optional; the copied prompt uses your values)

Adapted prompt2 variables
Review everything you remember or have been told about me, including {memory_sources}, and list the beliefs you rely on when you work for me.
Label each one: I said it directly, you inferred it, it applies only to one task or person, or you do not know where it came from. Quote the source where you can and never make one up.
Tell me which sources you could not open.
Rank the uncertain items by how much they could change your work on {main_tasks}, and ask me about the top five, one question each.
Do not edit or delete anything until I answer.

What can go wrong?

  • Accepting a saved memory as true because it is saved. The prompt deliberately treats stored items as unconfirmed until you say otherwise.
  • Letting the agent explain an unknown source with a plausible story. If it cannot point to the original message, treat the origin as unknown.
  • Answering vaguely. A short, specific correction such as only for work trips is easier for it to apply than a general preference.
  • Skipping it on shared or delegated accounts, where requests made for someone else are most likely to be stored as yours.

Our take

Memory makes agents more useful, but it also lets one offhand remark harden into a rule you never agreed to. Booking the cheapest room once becomes a standing preference, or a request you made for a colleague starts shaping your own plans. Fenech's audit is a careful fix because it asks for evidence rather than a tidy list. Each belief has to be labeled as said by you, guessed or of unknown origin, and the agent must admit when it cannot find the source instead of inventing one. The five-question limit is smart, too. Most people will never review fifty memories, but they will answer five ranked by impact. Two cautions. Some tools cannot show the agent all of its own memory, so read the note on what it could not inspect before trusting a clean result. And keep your answers specific, because a narrow correction is easier to apply than a broad one. In our dry run on a fictional consultant's assistant, it flagged a budget-hotel habit from one conference and a colleague's dietary request saved as the user's own, and changed nothing before asking.

Where the time goes back: Quietly wrong preferences cost time on every task they touch, from a hotel pick to the tone of a draft. A quarter-hour review catches them once instead of correcting the same output again and again.

FAQ

Will it delete or rewrite my memories during the audit?
No. The prompt tells it to change nothing until you have answered its questions.
Why only five items?
Five keeps the review short enough to finish. It ranks the uncertain beliefs by how much they could change its work, so the riskiest ones come first.
Does it need Grok Bot?
Fenech wrote it for Grok Bot, but any assistant with readable memory or saved instructions can run it. Results depend on how much of its own memory the tool can show.

Source and credit

The original prompt on this page is by Michael Fenech (@Michael_Fenech_), shown word for word with a link to where it was published. The summary, notes and adapted version are ours.

Original
X post: an Assumption Audit for what Grok Bot believes about you
Creator
Michael Fenech (@Michael_Fenech_)
Published on
X
Original date
Nov 13, 2026
License
Not openly licensed; the original prompt is shown word for word with credit and a link to the original
Originally for
Grok Bot
AI dry run
Nov 15, 2026: passed. Dry-run tested by our AI test agent on sample input. Correct labels, no invented provenance, real versus possible impact separated, nothing edited before answers.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Nov 15, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Talk through a meeting with your agent right after it ends

As soon as a client meeting, phone call or on-site visit wraps up, start a voice conversation with your agent, talk through what happened while it is fresh, and get back a written list of decisions, commitments, due dates and open questions plus a follow-up draft you check before anything is sent.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminWorkflow✓ AI dry run

Build a daily briefing from today's field-service jobs

From a day's job or call export, get an internal briefing that counts unique jobs, puts decisions and callbacks at the top, deduplicates repeat rows, flags incomplete or conflicting records instead of filling them in, and stays with named internal recipients. Nothing in the briefing is sent to customers.

Credit: Tyler Griffin (@TylerGriffin)

Minutes
Operations & AdminPrompt✓ AI dry run

Check an AI answer or plan before you act on it

Paste in an AI-made plan and get a short verdict: what is backed by evidence, what is contradicted, what is only a risk, and what to check next.

Credit: u/softdeveloper23 on r/PromptEngineering

Minutes
Operations & AdminPrompt✓ AI dry run

Decide if a task needs an AI agent or a plain automation

Describe a process and get a straight answer: plain rule-based workflow, AI for one step, or a full agent, with the reasons and a rough build plan.

Credit: u/Decent-Phrase-4161 on r/AI_Agents

Minutes
Operations & AdminPrompt✓ AI dry run

Find the old ChatGPT chats worth keeping before a cleanup

Before you bulk-delete a long ChatGPT history, have the assistant name the past conversations that hold the most work you would hate to redo, with a rough date and a few distinctive search terms for each, then confirm every one by opening it and save copies outside ChatGPT before deleting anything.

Credit: u/Ok_Negotiation_2587 on r/ChatGPT

Minutes