Public launch on WordPress.org. Refreshed listing assets and readme; no functional change and no migration \u2014 safe in-place upgrade.<\/p>","0.2.0":"
Adds AI Assistant Preview, WordPress Abilities API + MCP, and a multi-channel discovery sub-score, plus fixes for JSON-LD output, stale cron recovery, and Markdown cleanup. Safe in-place upgrade \u2014 the Context Score cache auto-invalidates.<\/p>","0.1.0":"
First public release. Install on WordPress 6.9+ with PHP 7.4+.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3589684,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3589684,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3589684,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3589684,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.4.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3589684,"resolution":"1","location":"assets","locale":"","width":1280,"height":720},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3589684,"resolution":"2","location":"assets","locale":"","width":1280,"height":720},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3589684,"resolution":"3","location":"assets","locale":"","width":1280,"height":720},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3589684,"resolution":"4","location":"assets","locale":"","width":1280,"height":720}},"screenshots":{"1":"Context Profile \u2014 the single source of truth for which CPTs and statuses are exposed to agents","2":"AI Assistant Preview \u2014 see exactly what an agent reads: raw HTML, the clean Markdown View, and the Mokhai is an open-source WordPress plugin that turns your site into a first-class citizen of the AI-agent web \u2014 readable today, actionable next. A single Context Profile<\/strong> (configured once under Tools \u2192 Context) is the source of truth for every agent-facing surface \u2014 what's exposed, how it's served, and how it's scored.<\/p>\n\n Mokhai ships seven coherent modules, all driven by one Context Profile:<\/p>\n\n The plugin is fully free, GPL-2.0+, with no paid tier and no hosted backend. Every module is independently toggleable from the Context Profile. No content leaves your server. The plugin makes no external HTTP calls; AI providers configured via the WP AI Client (an optional dependency) are only consulted by modules that explicitly opt in, and every deterministic surface (Markdown Views, \/llms.txt, the rule-based score, the gap-fill schema) runs fully locally without an AI provider.<\/p>\n\n Markdown Views exposes any public URL as a clean Markdown variant. The intended consumer is an AI agent that's discovered a URL (typically via \/llms.txt) and wants the raw content without HTML chrome, header\/footer\/sidebar markup, or JavaScript-rendered widgets.<\/p>\n\n All three return the same body. Pick whichever matches your client.<\/p>\n\n The 200 response always carries A URL returns 404 with no body \u2014 never a partial content leak \u2014 when any of the following is true:<\/p>\n\n All denial paths produce the same 404 shape \u2014 admin debugging via the REST endpoint or the Mokhai publishes a Most sites have URLs that aren't WordPress posts but are valuable agent context \u2014 pricing pages, brand guidelines, support knowledge bases hosted elsewhere. The editorial entries admin UI lets site owners add curated entries with custom titles and descriptions; they appear in Optionally, an LLM pass drafts the per-entry descriptions from the post content (uses the WP AI Client provider configured at the site level). The deterministic floor \u2014 title-only, no description \u2014 runs without an AI provider.<\/p>\n\n Posts whose body is below a minimum length are skipped by the LLM pass rather than padded with filler (e.g. a bare \"Title is available at URL.\"). Such entries show a \"skipped\" status in the Descriptions tab and fall back to the title-only floor in Context Score is the 0\u2013100 readiness audit answering \"how prepared is this site for AI agent traffic?\". It combines seven weighted sub-scores:<\/p>\n\n The score is surfaced in three places:<\/p>\n\n An LLM-generated narrative (uses the WP AI Client provider) explains the score in plain English and names the highest-leverage fixes. A rule-based narrative ships as a fallback for sites without an AI provider configured.<\/p>\n\n When you have an SEO plugin (Yoast, Rank Math, AIOSEO, The SEO Framework) active and emitting JSON-LD, Mokhai defers schema emission to them entirely \u2014 no competing markup, no duplicate type declarations. When no SEO plugin is emitting schema, Mokhai can optionally emit a native WebSite + Organization + per-content schema set so the schema sub-score in Context Score is achievable without a third-party SEO plugin. The toggle lives in the Context Profile; default is off (gap-fill behaviour kicks in only when explicitly enabled).<\/p>\n\n The AI Assistant Preview pane (Tools \u2192 Context) answers a question every site owner eventually asks: \"what does an AI assistant actually see when it reads this page?\" Pick any exposed URL and the pane renders three views side by side \u2014 the raw HTML, the Markdown View an agent fetches (proxied through the same converter as the live Mokhai registers an Mokhai stores rendered Markdown in a custom table named Context Score audit results are cached in the No content leaves your server. The plugin makes no external HTTP calls and ships no third-party analytics. AI providers configured via the WP AI Client (an optional dependency) are only consulted by modules that explicitly opt in; the deterministic surfaces (Markdown Views, \/llms.txt, rule-based score narrative, gap-fill schema) all run fully locally without an AI provider.<\/p>\n\n Both cache tables are dropped on plugin uninstall (not on deactivation \u2014 deactivate is reversible, uninstall is the explicit \"I'm done\" gesture).<\/p>\n\n Under Tools \u2192 Context<\/strong>, set:<\/p>\n\n The same screen exposes the LLM cleanup toggle (Markdown Views auto-cleanup pass), the LLM descriptions toggle (auto-drafted To turn Markdown Views off without uninstalling:<\/p>\n\n The module respects the toggle without latency \u2014 flipping back to true is instant; the cache table is preserved across toggle cycles.<\/p>\n\n\n No. Every deterministic surface (Markdown Views, \/llms.txt floor, rule-based Context Score narrative, gap-fill JSON-LD emission) runs fully locally with no external calls. Modules that benefit from an LLM (the Markdown cleanup pass, \/llms.txt entry-description drafting, the LLM-narrated Context Score) require the optional WP AI Client to be configured, but each is independently toggleable and not load-bearing for the core agent-readiness contract.<\/p><\/dd>\n For JSON-LD: when an SEO plugin (Yoast, Rank Math, AIOSEO, The SEO Framework) is active, Mokhai emits nothing competing \u2014 schema is theirs. When no SEO plugin is emitting JSON-LD, you can optionally enable Mokhai's native gap-fill emission from the Context Profile. For noindex: Mokhai ships an \/llms.txt is one surface among several. Mokhai ships the integrated reading layer (Markdown views), the discovery layer (\/llms.txt with editorial entries and LLM-powered descriptions), the audit layer (Context Score across seven sub-scores), and the schema coordination layer as a single coherent unit driven by one Context Profile. Most existing plugins target one of these surfaces in isolation; Mokhai treats them as a coordinated stack.<\/p><\/dd>\n v0.2 shipped the AI Assistant Preview pane, the WordPress Abilities API + MCP integration, and the multi-channel discovery sub-score. Looking ahead: a fuller agent-actionable<\/em> layer (callable tools via WebMCP \/ Public-launch release.<\/strong> The plugin is now live on the WordPress.org Plugin Directory as \"Mokhai - Agent Readiness Kit\" (slug Rename to \"Mokhai - Agent Readiness Kit\"<\/strong> (text domain Also ships the following changes that landed on Rename to Agentable<\/strong> (text domain Polish release. Refinements surfaced through a full live UX walkthrough of the v0.2.0 admin surfaces \u2014 score-narrative correctness, clearer labels, and a more discoverable plugin. Also renamed to \"AgentReady \u2013 AI Readiness Kit\"; REST, WP-CLI, and stored data keys are unchanged. (#224, AgDR-0059)<\/p>\n\n Improved<\/strong><\/p>\n\n Fixes<\/strong><\/p>\n\n Feature release. Three new agent-facing modules plus a batch of correctness fixes surfaced through live testing.<\/p>\n\n New<\/strong><\/p>\n\n Improved<\/strong><\/p>\n\n Fixes<\/strong><\/p>\n\n Bug-fix release. Four issues surfaced during post-merge smoke testing of v0.1.0 (PR #102 rebrand bundle) and the external LLM review of the live Fixes<\/strong><\/p>\n\n\/llms.txt<\/code> line, side by side","3":"LLMs Index \u2014 \/llms.txt<\/code> admin UI with editorial entries and LLM-powered descriptions","4":"Context Score \u2014 0\u2013100 readiness audit with seven sub-scores and actionable fixes"}},"plugin_section":[],"plugin_tags":[15643,2353,244604,4608,1117],"plugin_category":[55],"plugin_contributors":[246178],"plugin_business_model":[],"class_list":["post-326172","plugin","type-plugin","status-publish","hentry","plugin_tags-agents","plugin_tags-ai","plugin_tags-llms-txt","plugin_tags-markdown","plugin_tags-schema","plugin_category-seo-and-marketing","plugin_contributors-mokhaled","plugin_committers-mokhaled"],"banners":{"banner":"https:\/\/ps.w.org\/mokhai-agent-readiness-kit\/assets\/banner-772x250.png?rev=3589684","banner_2x":"https:\/\/ps.w.org\/mokhai-agent-readiness-kit\/assets\/banner-1544x500.png?rev=3589684","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/mokhai-agent-readiness-kit\/assets\/icon-128x128.png?rev=3589684","icon_2x":"https:\/\/ps.w.org\/mokhai-agent-readiness-kit\/assets\/icon-256x256.png?rev=3589684","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/mokhai-agent-readiness-kit\/assets\/screenshot-1.png?rev=3589684","caption":"Context Profile \u2014 the single source of truth for which CPTs and statuses are exposed to agents"},{"src":"https:\/\/ps.w.org\/mokhai-agent-readiness-kit\/assets\/screenshot-2.png?rev=3589684","caption":"AI Assistant Preview \u2014 see exactly what an agent reads: raw HTML, the clean Markdown View, and the \/llms.txt<\/code> line, side by side"},{"src":"https:\/\/ps.w.org\/mokhai-agent-readiness-kit\/assets\/screenshot-3.png?rev=3589684","caption":"LLMs Index \u2014 \/llms.txt<\/code> admin UI with editorial entries and LLM-powered descriptions"},{"src":"https:\/\/ps.w.org\/mokhai-agent-readiness-kit\/assets\/screenshot-4.png?rev=3589684","caption":"Context Score \u2014 0\u2013100 readiness audit with seven sub-scores and actionable fixes"}],"raw_content":"\n\n
.md<\/code> path, ?format=md<\/code> query, Accept: text\/markdown<\/code> content negotiation) and uniform 404 on denial. Per-post cache with content-hash invalidation, Gutenberg sidebar preview, WP-CLI command, REST endpoint for admin tooling.<\/li>\n\/llms.txt<\/code> generator that publishes a discovery surface for AI agents, with conflict detection against robots.txt<\/code>, an editorial entries admin UI for site owners to add curated entries, and an optional LLM-powered pass that drafts entry descriptions from post content.<\/li>\nwp ai-readiness-kit context-score recompute<\/code>. Includes an optional LLM-generated narrative (with a rule-based fallback) explaining the score and the highest-leverage fixes.<\/li>\n\/llms.txt<\/code> line side by side, plus an on-demand \"sample AI summary\" so you can sanity-check what an agent would say about the page.<\/li>\n\/llms.txt<\/code> regenerate, Markdown preview) through the WordPress Abilities API, and surfaces them to MCP clients via the WordPress MCP adapter. Every ability is manage_options<\/code>-gated.<\/li>\nai.txt<\/code>, \/.well-known\/<\/code> declarations, OpenAPI) beyond \/llms.txt<\/code>, so a site running several discovery channels scores higher than one running only one.<\/li>\n<\/ul>\n\nMarkdown Views<\/h3>\n\n
Three URL forms<\/h4>\n\n
\n
https:\/\/example.com\/about-us.md<\/code> \u2014 path-form (requires pretty permalinks; aligned with the llms.txt ecosystem convention)<\/li>\nhttps:\/\/example.com\/about-us\/?format=md<\/code> \u2014 query-form (works regardless of permalink structure)<\/li>\nAccept: text\/markdown<\/code> header on the canonical URL \u2014 content-negotiation form<\/li>\n<\/ul>\n\nContent-Type: text\/markdown; charset=utf-8<\/code>, X-Robots-Tag: noindex<\/code> (so search engines don't index the raw view as a duplicate of the HTML), and Cache-Control: no-store, must-revalidate<\/code>.<\/p>\n\nExposure rules<\/h4>\n\n
\n
publish<\/code> only)<\/li>\nagentready_post_is_noindexed<\/code> filter returns true (the extension point for SEO-plugin noindex coordination \u2014 wire it from your theme \/ a companion plugin in v0.1; native Yoast \/ Rank Math \/ AIOSEO subscribers ship in a follow-up release)<\/li>\nwp ai-readiness-kit md preview<\/code> command surfaces the specific reason.<\/p>\n\nInspection surfaces<\/h4>\n\n
\n
wp ai-readiness-kit md preview <post-id-or-url><\/code>. Supports --format=wrapped<\/code> for YAML-front-matter output suitable for piping into LLM tooling, --show-meta<\/code> for cache diagnostics on stderr, and --bypass-exposure<\/code> (requires manage_options) for inspecting hidden posts without serving them.<\/li>\nGET \/wp-json\/ai-readiness-kit\/v1\/markdown-views\/preview?post=<id><\/code>. Authentication via WP cookie \/ nonce; permission gated on edit_post<\/code> for the target post. Used by the Gutenberg sidebar; available to third-party admin tooling.<\/li>\n<\/ul>\n\nLLMs Index (\/llms.txt)<\/h3>\n\n
\/llms.txt<\/code> discovery surface for AI agents \u2014 the de-facto convention for declaring which URLs on a site are worth fetching as agent context. The generator is driven by the Context Profile: only CPTs and statuses you've exposed appear in the index. Conflict detection surfaces when robots.txt<\/code> already covers the same paths; an admin notice points to the conflict so coverage isn't silently inconsistent.<\/p>\n\nEditorial entries<\/h4>\n\n
\/llms.txt<\/code> alongside the auto-generated post entries.<\/p>\n\nLLM-powered descriptions<\/h4>\n\n
\/llms.txt<\/code>. Adjust the threshold with the agentready_description_min_content_chars<\/code> filter.<\/p>\n\nWP-CLI<\/h4>\n\n
\n
wp ai-readiness-kit llms-txt status<\/code> \u2014 current generation state, conflict report, entry count<\/li>\nwp ai-readiness-kit llms-txt regen<\/code> \u2014 force regeneration<\/li>\nwp ai-readiness-kit llms-txt preview<\/code> \u2014 output the current \/llms.txt<\/code> content to stdout<\/li>\n<\/ul>\n\nContext Score<\/h3>\n\n
\n
\/llms.txt<\/code> cache populated, at least one CPT exposed, entries published, no rewrite conflicts overriding the route<\/li>\npublish<\/code> (no risky non-publish exposures) and at least one CPT is configured explicitly rather than implicitly<\/li>\n\/llms.txt<\/code> conflicts are unresolved<\/li>\n\/llms.txt<\/code>, ai.txt<\/code>, \/.well-known\/ai-layer<\/code>, \/.well-known\/llms-policy.json<\/code>); all four = 100, so a plugin-only site can reach full marks. OpenAPI is detected and credited as a bonus channel for sites exposing an API but does not change the score. Sibling-provider plugins (e.g. AI Layer) are detected and credited via the filterable ai_readiness_kit_multi_channel_providers<\/code> registry.<\/li>\n<\/ol>\n\n\n
wp ai-readiness-kit context-score recompute<\/code> for scripted audits<\/li>\n<\/ul>\n\nSchema Coordination<\/h3>\n\n
AI Assistant Preview<\/h3>\n\n
.md<\/code> surface, so the no-hallucination guard applies), and the exact \/llms.txt<\/code> line for that entry. A \"Sample AI Summary\" box generates an on-demand, synchronous summary using the configured WP AI Client provider (no cron, no background queue \u2014 it runs and caches in place), so you can sanity-check the agent's-eye view of a page before publishing. The summary degrades gracefully (a structured hint, never a raw error) when no AI provider is configured.<\/p>\n\nAgent Abilities (MCP)<\/h3>\n\n
ai-readiness-kit<\/code> ability category and five core WordPress Abilities (WP 6.9+): audit-run, profile-read, profile-set-exposure, llms-txt-regenerate, and md-view-preview. Each is a thin wrapper over an existing service, gated on manage_options<\/code>, and exposed via the core wp-abilities\/v1<\/code> REST surface. When the WordPress MCP adapter is installed, these abilities are also reachable by MCP clients (the abilities are flagged meta.mcp.public<\/code>), making the plugin's operations callable by agent runtimes \u2014 a step from agent-readable<\/em> toward agent-usable<\/em>. The MCP flag is inert when no adapter is present, so the abilities work standalone.<\/p>\n\nPrivacy and Storage<\/h3>\n\n
{$wpdb->prefix}agentready_md_cache<\/code>, with one row per published post that has been requested at least once as Markdown \u2014 holding the Markdown body, an integrity hash of the source content, and the timestamp at which it was generated. The cache is invalidated automatically when a post is saved, trashed, or deleted.<\/p>\n\nagentready_context_score_cache<\/code> wp_options<\/code> entry (the most-recent breakdown only \u2014 overwritten on each recompute).<\/p>\n\nConfiguration<\/h3>\n\n
\n
publish<\/code> only.<\/li>\n<\/ul>\n\n\/llms.txt<\/code> entry descriptions), and the native Schema emission toggle (default off \u2014 opt in to satisfy Context Score's schema sub-score without a third-party SEO plugin). Each toggle gracefully degrades when the WP AI Client is unconfigured.<\/p>\n\nwp eval \"$p = get_option('agentready_context_profile'); $p['markdown_views_enabled'] = false; update_option('agentready_context_profile', $p);\"\n<\/code><\/pre>\n\n\n
Does Mokhai require an AI API key?<\/h3><\/dt>\n
How does Mokhai interact with my SEO plugin?<\/h3><\/dt>\n
agentready_post_is_noindexed<\/code> filter the Markdown Views handler honours; v0.1 leaves the SEO-plugin subscriber unwired (a theme or companion plugin can subscribe it today; native Yoast \/ Rank Math \/ AIOSEO subscribers ship in a follow-up release).<\/p><\/dd>\nHow is this different from existing \/llms.txt plugins?<\/h3><\/dt>\n
What's on the roadmap after v0.2?<\/h3><\/dt>\n
navigator.modelContext<\/code>), agent-activity analytics (per-bot counters), and a richer \/.well-known\/llms-policy.json<\/code> policy-declaration surface.<\/p><\/dd>\n\n<\/dl>\n\n\n0.4.0 \u2014 2026-06-29<\/h4>\n\n
mokhai-agent-readiness-kit<\/code>). This release is launch housekeeping \u2014 no functional change, no migration:<\/p>\n\n\n
mokhai-agent-readiness-kit<\/code> name (Plugin URI, package metadata). REST routes, WP-CLI commands, abilities, option keys, and all stored data are unchanged \u2014 existing installs upgrade in place with no action required.<\/li>\n<\/ul>\n\n0.3.2 \u2014 2026-06-21<\/h4>\n\n
mokhai-agent-readiness-kit<\/code>). wp.org plugin review rejected \"Agentable\" as colliding with existing third-party projects and required a name and slug that are clearly ours, with a distinctive leading term. \"Mokhai\" satisfies that. REST, WP-CLI, abilities, option keys, and all stored data are unchanged \u2014 existing installs upgrade with no migration. (#259, AgDR-0062)<\/p>\n\nmain<\/code> since 0.3.1:<\/p>\n\n\n
\/llms.txt<\/code> now warns in the admin when a static robots.txt<\/code> blocks the \/llms.txt<\/code> reference, so the conflict isn't silent. (#245, #250)<\/li>\n\/llms.txt<\/code> emits the site header on an otherwise-empty index instead of returning a blank body. (#244, #249)<\/li>\n\/llms.txt<\/code> index. (#243, #248)<\/li>\npost_title<\/code> when a filtered title comes back empty, so titled posts no longer render untitled. (#242, #247)<\/li>\n0.3.1 \u2014 2026-06-14<\/h4>\n\n
agentable<\/code>). The previous \"AgentReady\" brand collided with an existing third party (agentready.org), so the plugin is renamed to a distinct, ownable name that also fits the roadmap \u2014 sites readable today, actionable next. REST, WP-CLI, abilities, and stored data keys are unchanged, so existing installs upgrade with no migration. Also makes root-served-file detection (llms.txt<\/code>, ai.txt<\/code>, .well-known\/*<\/code>) subdirectory-install aware via get_home_path()<\/code> instead of assuming the install root is the web root. (#230, AgDR-0060)<\/p>\n\n0.3.0 \u2014 2026-06-12<\/h4>\n\n
\n
\/llms.txt<\/code>, ai.txt<\/code>, \/.well-known\/ai-layer<\/code>, \/.well-known\/llms-policy.json<\/code>) now score 100 on their own; OpenAPI is credited as a bonus channel for API-exposing sites rather than capping the score at 80. (#212, AgDR-0058)<\/li>\n\/llms.txt<\/code> description coverage). Internal key unchanged. (#211)<\/li>\nagentready_description_min_content_chars<\/code>. (#214)<\/li>\n<\/ul>\n\n\n
multi_channel_discovery<\/code> key. (#210)<\/li>\n_n()<\/code> plural forms (\"1 minute ago\" \/ \"5 minutes ago\"); excluded posts in the Descriptions table are labelled \"excluded\" and the intro copy matches. (#215)<\/li>\n<\/ul>\n\n0.2.0 \u2014 2026-06-03<\/h4>\n\n
\n
\/llms.txt<\/code> line, side by side) with an on-demand synchronous \"sample AI summary\". No cron; degrades gracefully without an AI provider. (#45)<\/li>\nmanage_options<\/code>-gated abilities (audit-run, profile-read, profile-set-exposure, llms-txt-regenerate, md-view-preview) exposed via core wp-abilities\/v1<\/code>, and reachable by MCP clients through the WordPress MCP adapter when installed. (#21, #131)<\/li>\n\/llms.txt<\/code> (ai.txt<\/code>, \/.well-known\/<\/code> declarations, OpenAPI), with a filterable sibling-provider registry. Discoverability re-weighted 20 \u2192 10 to fund it; total stays 100. (#22)<\/li>\n<\/ul>\n\n\n
Engine::WEIGHTS<\/code>). (#137, #139, #140)<\/li>\n<\/ul>\n\n\n
esc_html()<\/code> (angle brackets escaped via JSON_HEX_TAG<\/code>), so the structured-data payload validates in every standards-compliant validator. (#118)<\/li>\n\/llms.txt<\/code> recompute, Context Score recompute, Markdown cleanup, description generation) \u2014 fixes \"stuck pending forever\" on sites where wp-cron sat stale. (#115, #120, #121)<\/li>\n\/llms.txt<\/code> entry descriptions via a shared helper. (#145, #147)<\/li>\n\/llms.txt<\/code> now recomposes when a post's description changes, and carries a generator-version staleness signal so out-of-date descriptions are detectable. (#149, #151)<\/li>\npackage.json<\/code> version now tracks the plugin version (was drifting at 0.1.0). (#113)<\/li>\n<\/ul>\n\n0.1.1 \u2014 2026-05-24<\/h4>\n\n
\/llms.txt<\/code> output.<\/p>\n\n\n
\/llms.txt<\/code> regen now fires reliably after Context Profile saves on sites where wp-cron sits stale (e.g. wp-env without traffic, any site where cron failed for a window).