coleam00/archon for Claude Code: Contributor Tools or General Skills?

What is the coleam00/archon plugin, actually

coleam00/archon is the source repository for Archon, described in its own summary as the first open-source harness builder for AI coding, built to make AI coding deterministic and repeatable rather than a one-off chat session (23,273 GitHub stars). The Claude Code plugin inside that repository is not the Archon product wrapped as a skill. It is 46 components, 14 skills, 13 agents, and 19 commands, and most of them exist to help someone work on Archon's own codebase, workflows, or bugs.

Archon itself, per archon-dev's own description, is a remote coding agent: a platform run through a CLI called archon, with its own frontend, backend, workflow engine, and isolation layer. This plugin is the working set coleam00 built while shipping that platform, published rather than kept private.

Who is this plugin actually for?

Split the 46 components by what they assume before you install it. About a third name Archon, its CLI, or one of its internal subsystems directly, and only do something with Archon's own source checked out. The rest never mention Archon at all: general-purpose engineering skills, agents, and commands that read the same on Archon or on your own repository.

The Archon-specific components

The archon skill runs and creates Archon workflows and commands and manages Archon's own configuration. manage-run inspects, monitors, starts, approves, and controls Archon workflow runs through the archon CLI over bash. archon-dev is the primary skill for developing Archon's own code and routes to specialized guides depending on what you're trying to do.

Five commands prime an agent with one slice of Archon's own codebase before you touch it: prime for the whole thing, prime-frontend for the React web UI, prime-backend for the core and server, prime-workflows for the workflow engine, and prime-isolation for its isolation system and git operations. plan-feature writes an implementation plan for an Archon feature, and execute runs an existing Archon plan file.

Validation and release get their own components. validate runs Archon's validation suite with a report per level, and validate-2 is broader: an end-to-end check of the platform covering Docker, a test adapter, the database, and a full GitHub workflow run. validate-ui audits the Archon web interface through browser automation. release cuts a patch, minor, or major release from the dev branch, writes the changelog, and opens the PR to main, and test-release then verifies that the released archon binary works through a specific install path. replicate-issue spins up Archon and re-tests a reported GitHub issue's symptoms with browser automation.

The components that work on any codebase

For review and quality: code-reviewer and the code-review command check guideline compliance and bugs, code-review-fix fixes what a review found, rulecheck and its companion rulecheck-agent scan for rule violations and fix the highest-impact ones in an isolated worktree before opening a PR, silent-failure-hunter looks for swallowed errors and bad fallbacks, type-design-analyzer rates a type's encapsulation and invariants, code-simplifier proposes simplifications without changing behavior, and comment-analyzer catches comments that no longer match the code.

For understanding a codebase you didn't write: codebase-explorer finds where code lives and how it's built, codebase-analyst traces data flow with file and line references, docs-impact flags documentation a change left stale, and web-researcher searches for current docs and APIs and cites its sources.

For a bug end-to-end: rca documents a root cause for a GitHub issue, implement-fix builds the fix from that document, triage and triage-agent apply type, effort, priority, and area labels to issues, and pr-test-analyzer rates a pull request's test coverage before it ships.

Rounding it out: commit writes an atomic commit, handoff writes a session handoff document, execution-report reflects on completed work in a report, review-doc and system-review critique a document or a finished implementation against its plan, create-command generates new slash commands, save-task-list keeps a task list across sessions, sdk-verifier checks a TypeScript Agent SDK app before deployment, docker-extend personalizes the Docker dev container, and remotion-best-practices covers Remotion video work in React.

Why do agent-browser and playwright-cli look identical?

agent-browser and playwright-cli carry the exact same description in what Flowy indexed: automating browser navigation, form filling, screenshots, and data extraction for web testing. The fact pack does not explain why the plugin ships both under separate names, so treat them as one browser automation capability reachable two ways rather than two different tools.

How do I install it

Flowy indexes coleam00/archon from its public GitHub repository. It does not host, bundle, or modify any of these 46 components, so what you get is whatever the repository ships. Install from the listing page linked at the top of this guide, and check whether the Archon-specific or the general-purpose half is the one you actually need.