Agentimus abilities, governed through the Bridge

What has to be true first

Needs WordPress 6.9 or newer (for the Abilities API) with Agentimus active. The 25 read abilities and the two always-on JSON resources require manage_options except check-page, read-content, and suggest-internal-links, which require edit_post on the specific page; the two llms.txt resources are public with no capability check; every write ability requires manage_options except update-content, edit-content, describe-content-image, write-description, write-topics, and write-search-fields, which require edit_post on the target page, create-content, which requires that page type's own create capability, and describe-image, which requires edit_post on the resolved attachment (or upload_files when the target cannot be resolved).

• The llms-txt resource ability only registers when the plugin's 'enable_llms_txt' setting is on
• The llms-full-txt resource ability additionally needs 'enable_llms_full' on top of 'enable_llms_txt'
• The 14 write abilities (create-content, update-content, edit-content, describe-content-image, describe-image, write-description, write-topics, write-search-fields, apply-fix, set-aside-page, dismiss-search, retry-announcement, review-client, recheck-client) only register when BOTH 'enable_mcp_server' and 'enable_agent_writes' are switched on in the plugin's settings

A note on the count below

The draft could not enumerate ids from truncated evidence and marked this dynamic with an empty list; the full source shows a private add() helper called 43 times with literal string slugs (25 read, 2 always-on JSON resources, 2 conditional llms.txt resources, 14 conditional write abilities), each with an explicit readonly/destructive pair, so nothing here is inferred.