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/commit.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/commit)<a href="https://agentmods.dev/commands/coleam00/archon/commit"><img src="https://agentmods.dev/badge/commands/coleam00/archon/commit/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/commit"><img src="https://agentmods.dev/badge/commands/coleam00/archon/commit.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.00579 |
| Opus 5.5 | $0.00003 | $0.00232 |
| Sonnet 5.5 | $0.00001 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
commit scanned grade A with 0 findings 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 12d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- commit — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Changes
Process
1. Review Changes
git status
git diff HEAD
git diff --stat HEAD
Check for new untracked files:
git ls-files --others --exclude-standard
2. Stage Files
Add the untracked and changed files relevant to the current work.
Do NOT stage:
.envor credential files- Large binary files
- Files unrelated to the current task
3. Create Commit
Write an atomic commit message with a conventional commit tag:
feat:— New capability or featurefix:— Bug fixrefactor:— Code restructure without behavior changedocs:— Documentation onlytest:— Test additions or fixeschore:— Build, CI, tooling changesperf:— Performance improvement
For monorepo changes spanning multiple packages, note the primary package in the scope:
feat(workflows): add DAG condition evaluator
fix(web): resolve SSE reconnection on navigation
refactor(isolation): simplify worktree resolution order
Commit message format:
tag(scope): concise description of what changed
[Optional body explaining WHY this change was made,
not just what changed. Include context that isn't
obvious from the diff.]
[Optional: Fixes #123, Closes #456]
4. Capture AI Context Changes
If any AI context assets were modified in this commit, add a Context: section to the commit body:
feat(orchestrator): add retry logic for session recovery
Added exponential backoff when SDK subprocess crashes mid-session.
Previously a single crash would fail the entire workflow.
Context:
- Updated .claude/rules/orchestrator.md with retry conventions
- Added .claude/commands/debug-session.md for session state inspection
- Surfaced issue: mock.module() in retry tests needs isolated batch
Fixes #482
What counts as AI context changes:
.claude/rules/— on-demand conventions added, updated, or removed.claude/commands/— slash commands created or modified.claude/docs/— reference docs added or updatedAGENTS.md— global rules changes.archon/workflows/or.archon/commands/— workflow or command definitions
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.
- 12d ago Changed 765309931fe1
- 1mo ago First seen · 87 lines · 7 tokens per session scan A f98227f52ed9
commit 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 579 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. 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.
release
Release all packages at specified version.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
commit
Git commit command - creates conventional commits.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.