itisagentready

Claude Code plugin. Audits a website's AI-agent readiness and fixes it end to end using the agent-site-orchestrator engine.

What it does

Two-layer model: a presentation layer (human-readable, aesthetic) and an agent-surface layer (machine-readable: MCP server card, A2A card, WebMCP, Agent Skills, OAuth discovery, schemas, …). The orchestrator wraps the 20 Mahoney Context Protocol generators, runs an agent-readiness-probe gate between every step, drives a single site.yaml manifest, renders design hints into the human layer, redeploys, and rescans until the agent surface actually handshakes — not just until files exist.

Commands

• /orchestrate <url> [--dry-run] — full audit → fix → redeploy → rescan loop
• /audit <url> — read-only bulk scan + deep probe, no changes
• /generate <name|all> — run the mcp-foundation generator surface into staging

Subagents

• audit-verifier — read-only grader (sonnet)
• orchestrator — worktree-isolated engine (opus)
• fixer — worktree-isolated remediation on a failed probe gate (opus)

Engine

scripts/orchestrate.py (+ scripts/artifact-map.json). mcp-foundation's CLI is monolithic; the engine generates once to staging then activates one generator group at a time with a probe gate between each (faithful to the "probe between every step" decision without forking cli.ts).

Status

• Engine: built, dry-run-verified (real mcp-foundation pass, 20 generators sequenced, manifest persisted).
• UI tier (AG-UI operator surface + MCP Apps SEP-1865 sandboxed tier): stub pending spec pinning — see docs/ui-tier-spec-pins.md. Not implemented from memory by design.
• Live /orchestrate runs require deployed targets; deploy is checkpointed.

Install

/plugin install from the MahoneyContextProtocol marketplace once published (marketplace.json is prepared locally; publishing to GitHub is a checkpointed external action and has not been performed).