harness-designing-plugin vs Agent-Native Plan
harness-designing-plugin is a plugin bundle for AI coding tools published by BilLogic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Agent-Native Plan is an MCP server published by BuilderIO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
| Marketplace |  harness-designing-plugin |  Agent-Native Plan |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 3.0.0 Forks (GitHub): 0 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 665 Stars (GitHub): 7 326 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
| Fact | harness-designing-plugin | Agent-Native Plan |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 (worse) | 7 326 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 665 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.context7.com/mcp) | Remote server (plan.agent-native.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/billogic/harness-designing-plugin | github.com/builderio/agent-native |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 30 h ago | not checked yet |
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
harness-designing-plugin
Harness Designing Plugin helps design teams turn their scattered AI setup — Notion prompts, Figma comments, AGENTS.md rules, chat histories — into a five-layer design harness that compounds across sessions and rotations. Four skills walk you through the assembly: • /hd:learn — Q&A about the five-layer concept (Context Engineering, Skill Curation, Workflow Orchestration, Rubric Setting, Knowledge Compounding) • /hd:setup — detects existing harness artifacts, pre-analyzes all five layers in parallel (5× harness-auditor + rubric-recommender), then walks you through link / critique / scaffold / skip per layer • /hd:maintain — captures lessons and promotes them to team rules in AGENTS.md with SHA-256 plan-hash proof-of-consent • /hd:review — audits harness health in a 2-batch parallel dispatch (5 layer-specialist agents + 2–3 context agents); critiques harness artifacts against quality rubrics Ships 9 sub-agents and 14 starter rubrics (distilled from pbakaus/impeccable, Nielsen's 10 heuristics, Material 3, Fluent
Agent-Native Plan
Structured visual plans and PR recaps with diagrams, prototypes, annotations, and sharing
How to run each
harness-designing-plugin As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install harness-designing-plugin@claude-communityAgent-Native Plan As a remote MCP server
claude mcp add --transport http agent-native-plan https://plan.agent-native.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only harness-designing-plugin has a remote endpoint we check. How we check endpoints
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: harness-designing-plugin · What it can do: Agent-Native Plan · 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.