Auxot
Tutorials Docs Pricing Login

Audit and clean up your agents

Build an Agent Audit that reviews your custom agents, surfaces overlap and decay, and tells you exactly what to delete, consolidate, or sharpen — then run it monthly.

Plus: three prompts that turn agent housekeeping into a recurring conversation rather than the thing you keep meaning to do.

Audience Admins · Everyone
Time ~15 min
Prerequisites An Auxot account with at least three custom agents you've built ([Create an agent from scratch](/tutorials/create-an-agent-from-scratch)). Helpful: [View your audit logs](/tutorials/view-your-audit-logs) if you want to feed the audit agent some real conversation data, and [Run a workflow](/tutorials/run-a-workflow) for the optional monthly scheduling.
You'll end up with An Agent Audit agent in your set, one completed review, and a clear sense of what to clean up before next month's run.

When a tutorial shows italic text in quotation marks, it usually mirrors a label or helper string inside Auxot. Product copy changes between releases — if something reads differently in your workspace, trust what you see on screen.

Callouts with a Worth knowing gold accent are meant as must-read context before you move on. Blockquotes that open with Tip are lighter, optional depth.

Why this matters

Agents accumulate. You build one for customer support, one for research, and one for contract review; within three months you have eight, two of them haven’t been used in weeks, two of them are doing each other’s jobs without you realizing it, and one of them is quietly answering questions it was never meant to handle.

Most people don’t audit their agents because the audit work is tedious: read each Description, recall what you actually use it for, compare against your other agents, and decide what to do. You can still get a structured pass without doing every comparison by hand: prompt the Admin Agent to spin up a dedicated Agent Audit agent, then open that agent and ask it to run the audit whenever you want a fresh inventory. Put it on a calendar rhythm you keep, or wire up the Run a workflow flow and Connect Slack to your agents once you’re ready for a trigger you own; nothing audits your agents in the background until something starts the job. Today, build that agent. By the end, your roster is cleaner and maintenance has a rhythm.

Quick start

  1. Sign in: open Auxot in your browser and log in.
  2. Open chat with the Admin Agent: click Chat in the left menu, make sure the agent picker reads “Admin Agent.”
  3. Ask him to build the Agent Audit: paste this: “Build me an agent called ‘Agent Audit.’ Its job is to read the Descriptions and context files of all my other agents, then tell me where they overlap, where any description is vague, where I’m missing an obvious agent, and which agents haven’t been used in 30 days. Make it ready to use.”
  4. Switch to chat with Agent Audit: pick it from the agent picker.
  5. Ask for the audit: “Run the audit. Be specific about which agents to consolidate, delete, or sharpen, and tell me what’s missing.”

Done? You have a punch list of recommendations from Agent Audit. Pick the obvious wins and act on them. The rest can wait for next month’s review.

The agent can do that?

Audit work scales with how often you do it; the longer between audits, the more there is to review. Paste these three prompts into chat, send them, then act on what comes back.

1. Have the Admin Agent compare two agents and recommend keep, merge, or split

Open chat with the Admin Agent and try this:

Look at my "[agent A]" and "[agent B]". Where do their jobs overlap? Where do they leave gaps? If you were running my business, would you keep both, merge them into one, split one of them into two, or delete one? Be specific about which fields to change in each case.

Why it’s non-obvious: Most people audit agents one at a time. The pairwise comparison surfaces overlap and gaps that single-agent reviews miss. The Admin Agent doesn’t just say “you have two marketing agents”; he tells you whether to merge them and which Description to keep, or to split one of them along a specific seam.

2. Have the audit agent post a monthly report to Slack on a schedule

Once the audit agent is built, you don’t want to remember to run it. Schedule it. Open chat with the Admin Agent:

I want my Agent Audit to run on the first Monday of every month and post the audit to my Slack #operations channel. What do I need to set up — a workflow, a scheduled job? Walk me through it.

Why it’s non-obvious: Workflows (Run a workflow), Slack (Connect Slack to your agents), and your audit agent stay separate until you sketch how they chain. Paste the prompt from the gray box above; use the outline to wire triggers you control (cron, intake, or a recurring calendar reminder) so the report lands without you manually remembering each run. Auxot doesn’t pick Mondays by itself.

3. Have the Admin Agent recommend the agents you don’t have but should

This is an inverted-usage move. Once your existing agents are clean, ask:

Looking at my agent set and what kind of work my business actually does — [briefly describe] — what agents am I missing? Which of these missing agents would be the highest-leverage to build first, and what would its description and context files look like?

Why it’s non-obvious: Audits usually focus on what to remove. This inverts: what should you add? After you send this prompt, the Admin Agent reads your existing agents as evidence of what you’ve prioritized, then names what’s conspicuously missing. Pairs well with power move 1: clean up first, build the next one second.

Go deeper

How often to audit

Monthly is enough for most setups. Weekly is overkill unless you’re building agents at a fast clip. Quarterly lets too many problems accumulate. The audit agent’s job is to make monthly cheap: once it’s built and scheduled, it costs you ten minutes to read the report and act on the obvious wins.

What goes wrong over time

Three patterns to watch for:

  • Overlap: two agents whose Descriptions are close enough that you can’t quickly tell which one to pick. Solution: merge or split along a clear line.
  • Scope creep: an agent that started narrow (“draft customer replies”) and accumulated extras (“and also analyze sentiment, and also draft pitch emails, and also…”). Solution: trim the Description back to original scope, or split.
  • Disuse: an agent you built once and haven’t used in 30+ days. Solution: delete or rename with an [archived] prefix so it falls out of your default picker.

When to consolidate vs delete vs sharpen

  • Delete when the agent has near-zero use AND its work is fully covered by another agent.
  • Consolidate when two agents are doing similar work but you’d lose nuance by collapsing them. Pick one’s Description as the base, fold the unique constraints from the other in, then delete the absorbed one.
  • Sharpen, don’t delete when the agent is used but answers feel generic. The fix isn’t deletion; it’s a tighter Description and better context files (Give your agent its job description).

The audit agent is itself an agent

The same governance applies: it has a Description, it can have context files, it can be sharpened over time. After your first audit, the obvious next step is to ask the Admin Agent to refine the audit agent’s Description based on what was useful in the report and what you ignored. Iterate on the auditor the way you iterate on any agent.

Troubleshooting

  • Agent Audit’s report is generic and not useful. Its Description probably doesn’t include enough about your business or your roster structure. Edit its Description to mention your team size, your industry, and what kinds of work your agents do. The report will sharpen on the next run.
  • Agent Audit keeps recommending the same things month after month. That’s not a bug; it’s signaling that you’re not acting on its recommendations. Either act on them, or update its Description to acknowledge constraints you’re working around (“don’t recommend deleting these two agents, they’re for a project that’s still active”).
  • You don’t know which agents are unused without checking each one. Ask the Admin Agent: “Which of my agents haven’t had a conversation in the last 30 days?” After you send that, he reasons over what your account exposes; cross-check against the View your audit logs walkthrough when you want to see receipts row by row.

Variations & edge cases

  • Free tier: Agent Audit works fine on Free tier. The 30-day usage check uses your audit logs which are available on every tier.
  • Multi-team setups (Business+): if your org has multiple teams (Set up multi-team isolation), each team has its own set. Either build a per-team Agent Audit scoped to that team, or one org-scoped Agent Audit that reviews everything.
  • The Admin Agent itself. Don’t audit the Admin Agent: he’s locked, you can’t change his Description, and his “scope” is system-wide by design. Skip him.
  • The first audit always finds the most issues. Subsequent audits find fewer because you’ve already cleaned up. Don’t be surprised when month two surfaces three issues instead of fifteen; that’s the system working.

Walkthrough

Step 1: Open chat with the Admin Agent

Click Chat in the left menu. Make sure the agent picker at the top reads “Admin Agent.”

Step 2: Build the Agent Audit

Paste this:

Build me an agent called "Agent Audit." Its job is to read the Descriptions and context files of all my other agents, then tell me where they overlap, where any description is vague, where I'm missing an obvious agent, and which agents haven't been used in 30 days. Give it a clear job description, attach any relevant context files, and make it ready to use.

The Admin Agent proposes the configuration (name, description, context files, and tool policy). Confirm by saying “yes, create it” or similar. The agent appears in Settings → Agents.

Tip: If you have a context file that describes your business or your team’s work, attach it to the audit agent. Its review will be sharper because it knows what your agents are supposed to be doing for you, not just what their Descriptions say.

Step 3: Switch to the Agent Audit

In the chat, click the agent picker and select Agent Audit. The chat thread is fresh; no history with this agent yet.

Step 4: Run the audit

Paste this:

Run the full audit. List every custom agent on my account. For each one, give me a one-line read on whether it's working well, going stale, or unused. Then recommend specific actions: delete, merge, sharpen, or leave alone. Be blunt. Don't pad.

The audit agent pulls your agent list, reads each Description and any attached context files, and produces the report. Read it carefully; at minimum, you’ll learn things you didn’t know about your own roster.

Step 5: Act on the obvious wins

From the audit, pick the moves that are obvious and easy:

  • Delete agents that haven’t been used in 30+ days AND duplicate work covered elsewhere.
  • Merge or split agents the audit flagged as overlapping.
  • Sharpen Descriptions for the agents flagged as too vague; Give your agent its job description covers the editing.

Save the harder decisions for later. The audit is advisory, not prescriptive; your judgment overrides.

Step 6: (Optional) Schedule it monthly

Use power move 2 above. After you paste and follow the outline, wire the audit agent into a workflow and Slack yourself (Run a workflow, Connect Slack to your agents). Once that’s live, maintenance runs on a schedule because your trigger fires, not because anything wakes up unattended.

What’s next

Reference

Browse all tutorials