When should you use it?
- Your weekly agent usage keeps climbing while the jobs stay the same
- Several routines click through websites even though you have connected the same apps
- You are not sure which logins and permissions your agents actually use
Not for: A single agent with one or two simple jobs, where a quick look at the run log is enough; Setups where the lead agent cannot see the other agents' routines at all; Teams that want changes made automatically, since the audit only reports and proposes
What do you need, and what do you get?
You need
- Access for your lead agent to the routines and run history it is allowed to inspect
- A list of the apps and accounts you have connected
- Three recurring jobs you are willing to test with an alternative method
You get
- An inventory of tools used per agent and per job
- A list of jobs using a heavier method than needed, with a lighter option for each
- Places where the agent trusts remembered facts instead of a live source
- Access and approval concerns, plus three measured experiments to run first
How does it work, step by step?
- Paste the auditGive Fenech's prompt to the agent that coordinates your others, such as a chief of staff agent.
- Read the inventoryCheck its list of tools per job against what you believe each routine does; gaps are findings too.
- Pick three testsApprove the three experiments it proposes, choosing jobs that run often and are easy to compare.
- Compare with the same inputsHave each old and new method run on identical inputs and record tool calls, time, accuracy and usage where it can be measured.
- Switch only on evidenceChange a routine only when the lighter method is at least as reliable, and keep a note of the fallback.
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, Claude Cowork, ChatGPT agent and others. Values in lime are placeholders.
Original prompt by Michael Fenech (@Michael_Fenech_)
Review how my Grok Bot team selects and uses tools. Start with recurring tasks and workflows you can inspect. Don't assume you have visibility into every Bot. 1: TOOL INVENTORY — Identify which apps, browser workflows, computer-use tasks and reusable skills each Bot relies on. 2: SIMPLEST RELIABLE METHOD — For each job, check whether a connected app can complete it directly. If not, consider an existing skill, a suitable script or browser automation before using full computer control. 3: SOURCE OF TRUTH — Identify workflows relying on remembered information that should instead be checked against live sources such as email, calendars, documents or connected systems. 4: REPEATED WORK — Find tasks where Bots repeatedly navigate the same screens, collect the same information or rebuild a process that could be reused. 5: ACCESS AND SECURITY — Check which accounts and permissions each workflow actually uses. Don't assume separate Bots have isolated computer access or logins. 6: FAILURE AND FALLBACK — Define what happens when the preferred tool is unavailable, returns incomplete information or requires a sign-in. Never silently substitute an unapproved method. 7: EFFICIENCY TEST — Select three suitable recurring jobs. Propose an alternative method for each, then compare tool calls, usage where measurable, completion time, accuracy and reliability using the same inputs. Give me a TOOL EFFICIENCY REPORT showing: • Workflows using unnecessarily complicated methods • Better tools or reusable methods to consider • Outdated information risks • Access and approval concerns • Three experiments worth running first Don't change workflows, permissions, skills or Bots without my approval. Don't claim usage savings unless we've measured them. After approval, test the alternatives safely and recommend changes only when the results are at least as reliable.
Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: a seven-point tool selection audit for a Grok Bot team.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Look at the recurring jobs you are able to inspect and tell me which ones you cannot see. For each job, list the tools it uses (connected app, saved skill, script, browser, full computer control) and say whether a lighter one would work just as reliably. Flag any job that relies on remembered information it should check against {live_sources} instead. Note the logins and access rights every job depends on and what it does when its main tool fails or asks for a sign-in. Pick {number} jobs that run often and design a fair comparison: same inputs, old method versus new, counting tool calls, time and errors. Report back without changing anything. Do not estimate savings you have not measured.
What can go wrong?
- The agent may not see every routine. Ask it to list what it could not inspect rather than assume full coverage.
- Savings guessed from a description are not savings. Insist on numbers from paired runs.
- A lighter tool can break silently when a site or app changes. Keep the fallback rule in each routine.
- Shared logins across agents are easy to miss. Treat any shared account as a finding to review.
Our take
Most usage problems in agent teams are not about the model; they are about the route the agent takes. A routine that opens a browser, signs in and scrolls a dashboard every morning can often get the same numbers from a connected app in one call. Fenech's audit is valuable because it names that hierarchy and then refuses to trust a hunch: the efficiency section asks for paired runs on the same inputs before anyone claims a saving. We also like the source-of-truth check, which catches routines that rely on something the agent remembered weeks ago instead of looking it up again, and the access section, which reminds you that separate agents may share one login. Our caution is scope. The lead agent can only audit what it can see, so read the list of what it could not inspect as carefully as the findings. In our dry run with a fictional marketing agency's five routines, the audit flagged a daily report pulled through a browser when the analytics app was connected, proposed it as the first experiment, and held every change for approval.
Where the time goes back: One report shows where routines waste effort, and three paired tests tell you which changes are worth making, so you stop paying for a heavier route on jobs that run every day.
FAQ
What counts as a heavier method?
Will it change my routines on its own?
Does this only work with Grok Bot?
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: a seven-point tool selection audit for a Grok Bot team
- Creator
- Michael Fenech (@Michael_Fenech_)
- Published on
- X
- Original date
- Nov 4, 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 5, 2026: passed. Dry-run tested by our AI test agent on sample input. Listed what it could not inspect, flagged the browser-based report despite a connected app, caught the stale remembered numbers and the shared login, proposed three fair paired tests and changed nothing.
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 5, 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.