Archon is a workflow engine for AI coding agents that turns development processes into YAML-defined sequences with phases, validation gates, and artifacts. Developers use it to run repeatable processes such as planning, implementation, testing, code review, and pull-request creation across projects. The catalogue entries provide commands, agents, skills, hooks, instructions, and settings for working with Archon.
Borrowing it
Nothing to install: this file belongs to coleam00/Archon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/coleam00/Archon/dev/.claude/commands/execute.mdgit clone --depth 1 https://github.com/coleam00/ArchonWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/coleam00/archon/execute)<a href="https://agentmods.dev/commands/coleam00/archon/execute"><img src="https://agentmods.dev/badge/commands/coleam00/archon/execute/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/coleam00/archon/execute"><img src="https://agentmods.dev/badge/commands/coleam00/archon/execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00007 | $0.01116 |
| Opus 5.5 | $0.00003 | $0.00446 |
| Sonnet 5.5 | $0.00001 | $0.00223 |
| Haiku 4.5 | $0.00001 | $0.00112 |
Grade A, and why
execute scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
{Any curl commands or UI steps to manually verify the feature works.} Copies of this mod
1 near-identical copy found in the catalogue:
- execute — 100% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute: Implement an Archon Plan
Objective
Read and execute every task in the plan file: $ARGUMENTS
Implement all tasks faithfully, following Archon monorepo conventions, and report results.
Step 1: Read the Entire Plan
Read the plan file at $ARGUMENTS from start to finish before writing a single line of code.
Understand:
- All tasks and their dependencies
- Affected packages and files
- Architecture notes and prohibited patterns
- The validation steps at the end
Do NOT start implementing until you have the full picture.
Step 2: Verify Current State
Check the working tree is clean before starting:
git status
If there are uncommitted changes unrelated to this plan, flag them before proceeding.
Check the current branch:
git branch --show-current
Step 3: Execute Tasks in Dependency Order
Work through each task in the plan sequentially (respecting Depends on: ordering).
For each task:
- Read the target file(s) before modifying — never edit blindly.
- Implement the change using the Edit or Write tools.
- Verify the change compiles after touching TypeScript files:
Fix type errors immediately — do not accumulate them.bun run type-check 2>&1 | tail -20
Archon conventions to follow:
Imports:
// Type-only imports
import type { IPlatformAdapter, Conversation } from '@archon/core';
// Value imports — named, not namespace
import { handleMessage, pool } from '@archon/core';
// Submodule namespace imports (acceptable)
import * as git from '@archon/git';
Functions:
async function createSession(id: string): Promise<Session> { ... }
// No implicit any
Logging:
import { createLogger } from '@archon/paths';
// Lazy logger pattern (test mocks work correctly)
let cachedLog: ReturnType<typeof createLogger> | undefined;
function getLog(): ReturnType<typeof createLogger> {
if (!cachedLog) cachedLog = createLogger('my-module');
return cachedLog;
}
// Event naming: {domain}.{action}_{state}
log.info({ id }, 'session.create_started');
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago Changed · -1 lines 92b11b4af728
- 4d ago Changed · -7 lines d0a2aae64eb9
- 1mo ago First seen · 190 lines · 7 tokens per session scan A 0ebb775661b6
execute is a command published in the GitHub repository coleam00/Archon (23,704 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 1,116 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
review-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
triage
Classify/label newly opened GitHub issues missing labels.
release
Release all packages at specified version.
cleanup
Autonomous cleanup-loop iteration: discover ONE target → complete execution → verify → report. Runs stateless: derive from current tree; assume prior runs left it consistent.
hatch3r-workflow
Guided development lifecycle with 4 phases (Analyze, Plan, Implement, Review) and scale-adaptive Quick Mode for small tasks; --plan-file executes an approved plan document without re-deriving it.