Get a whole-site content audit

Before you let an agent change anything, it helps to have it tell you what is actually on the site. Most people are surprised by at least one thing: a pile of drafts that never shipped, a custom post type they forgot existed, or a plugin still running that they meant to remove.

This is the orientation prompt. It reads the basics and hands you a briefing, and it cannot touch a thing.

Give me a one-page health check of this WordPress site. Read only, change
nothing. I want the site name, tagline, and language up top, then the counts
of posts and pages broken out by status (published, draft, pending, whatever
exists), the media library count by file type, the list of post types with a
note on which ones you are allowed to write to, the active theme, and the
plugins that are currently on. Lay it out as a short briefing I can skim in
under a minute, and put a one-line takeaway at the very top: anything that
looks off, like a stack of drafts that never got published or a plugin I
forgot was still running.

Why this is safe to run

Every ability behind this prompt is a read. Counting posts is a separate ability from listing them, and none of these can write, so the worst case is that an ability you left switched off quietly returns nothing. The post-type list carries a writable flag per type, so this one answer also shows you where the agent could write if you decided to let it later.

Already connected? Skip the paste. Ask your agent for the “whole-site content audit” recipe, or just ask it to describe your site, and it runs the same reads on your own install.