Ext Ops Panel
Open dashboard
Comparison

ai-coding-ok vs Agent Guardrails

ai-coding-ok is a plugin bundle for AI coding tools published by Mark7766. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Agent Guardrails is an MCP server published by logi-cmd. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceai-coding-okAgent Guardrails
Claude Code: claude-plugins-community Listed
Version: 4.1.0
Forks (GitHub): 3
Stars (GitHub): 16
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.3
Downloads/month (npm): 441
Downloads/week (npm): 53
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

ai-coding-ok vs Agent Guardrails
Factai-coding-okAgent Guardrails
Marketplaces that list it11
Stars (GitHub) (differs)16No figure on GitHub
Forks (GitHub) (differs)3No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (agent-guardrails)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/mark7766/ai-coding-okNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

ai-coding-ok

In its own words, on Claude Code: claude-plugins-community:

PDCA memory loop for Claude Code — prevents "AI fixed bug X and broke feature Y" across iterations. Installs a three-tier memory system in your project (project-memory, decisions-log, task-history) and enforces a closed PDCA loop on every task: Plan (read memory before coding), Do, Check, Act (write memory back after). The Act step is what most tools skip — without it, your context file rots after 10 iterations. With it, iteration 50 has the same context quality as iteration 1. Complements superpowers: superpowers brings per-session discipline, ai-coding-ok brings cross-session memory. Also works with Copilot, Cursor, and OpenCode via the same templates.

Agent Guardrails

In its own words, on Official MCP Registry:

Merge gates and safety checks for AI coding agents via MCP.

How to run each

ai-coding-ok As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ai-coding-ok@claude-community

Agent Guardrails As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-guardrails -- npx -y agent-guardrails

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: ai-coding-ok · What it can do: Agent Guardrails · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built