Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/coleam00/archon/primegit 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/prime)<a href="https://agentmods.dev/commands/coleam00/archon/prime"><img src="https://agentmods.dev/badge/commands/coleam00/archon/prime.svg" alt="Measured on agentmods" 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 | $0.00009 | $0.00604 |
| Opus 5 | $0.00005 | $0.00302 |
| Sonnet 5 | $0.00002 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
prime 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 4d 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:
- prime — 89% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prime: Load Archon Project Context
Objective
Build comprehensive understanding of the Archon monorepo before beginning any work. This orients you on structure, active state, and key architectural conventions.
Process
1. Analyze Project Structure
List the monorepo packages:
!ls packages/
Show workspace scripts:
!cat package.json | head -35
2. Read Core Documentation
Read CLAUDE.md in full — it contains the authoritative architecture reference, engineering
principles, import patterns, and development guidelines for this project.
3. Identify Key Entry Points
Read these files to understand the primary message and execution flow:
packages/core/src/orchestrator/orchestrator-agent.ts— single entry point for all platformspackages/core/src/handlers/command-handler.ts— slash command routing (no AI)packages/server/src/index.ts— server startup, adapter wiring, port allocationpackages/workflows/src/executor.ts— sequential/parallel/loop/DAG workflow execution
4. Understand Package Dependency Layers
Read the dependency chain (no @archon/* deps → most isolated):
packages/paths/src/index.ts— path resolution + Pino logger (zero deps)packages/git/src/index.ts— git ops (depends only on @archon/paths)packages/isolation/src/index.ts— worktree isolation (depends on @archon/git + @archon/paths)packages/workflows/src/index.ts— workflow engine (depends on @archon/git + @archon/paths)
5. Understand Current State
Check recent commits:
!git log -10 --oneline
Check current branch and working tree status:
!git status
List any active worktrees:
!git worktree list
Output Report
Provide a concise summary (under 300 words) covering:
Project Overview
- Archon: Remote agentic coding platform (Slack, Telegram, GitHub, Discord, Web)
- Bun + TypeScript monorepo with 8 packages: paths, git, isolation, workflows, core, adapters, server, web
- SQLite (default, zero-setup) or PostgreSQL (optional via DATABASE_URL)
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.
- 4d ago First seen · 76 lines · 9 tokens per session scan A 4824e9bff1ea
prime is a command published in the GitHub repository coleam00/Archon (23,366 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 604 once invoked, about $0.0000 per session on Opus 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
triage
Classify/label newly opened GitHub issues missing labels.
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.
cleanup
Autonomous cleanup-loop iteration: discover ONE target → complete execution → verify → report. Runs stateless: derive from current tree; assume prior runs left it consistent.
hello
Say hello.