harness-architect vs io.github.einvoice-dev1/archsteer
harness-architect is a plugin bundle for AI coding tools published by leee880619-commits. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.einvoice-dev1/archsteer is an MCP server published by einvoice-dev1. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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-architect |  io.github.einvoice-dev1/archsteer |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.6 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.0 Downloads/month (PyPI): 301 Downloads/week (PyPI): 46 Forks (GitHub): 0 Stars (GitHub): 5 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-architect | io.github.einvoice-dev1/archsteer |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 3 (worse) | 5 (better) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (archsteer) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 17 | 4 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/leee880619-commits/claudecode-harness-setup-assistant | github.com/einvoice-dev1/archsteer |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-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
harness-architect
harness-architect is a meta-tool that scans any target project and builds an end-to-end Claude Code harness — CLAUDE.md, settings, rules, agents, playbooks, hooks, and MCP — through a 9-phase orchestrated workflow. The plugin enforces a strict Agent-Playbook separation (WHO / HOW): agents define identity and hand off methodology to sub-agent-only playbooks, preventing the main session from bypassing guardrails. Every phase is reviewed by an independent red-team advisor that produces BLOCK / ASK / NOTE classifications, and cross-phase state is persisted to `docs/{request}/` so interrupted sessions resume deterministically. Target users: anyone — including non-developers — who wants a correct-from-day-one Claude Code setup on every new project without re-deriving the same 30-decision matrix each time. The plugin ships a 6-step "strict-coding" preset for complex coding projects and three Phase 1-2 branches (fresh setup / Cursor migration / harness audit).
io.github.einvoice-dev1/archsteer
Architecture governance for AI agents: query the live model, get target patterns, check files.
How to run each
harness-architect As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install harness-architect@claude-communityio.github.einvoice-dev1/archsteer As a local MCP server: PyPI package
claude mcp add --transport stdio archsteer -- uvx archsteer mcpCommands 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: harness-architect · What it can do: io.github.einvoice-dev1/archsteer · 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. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.