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/context-engineering-intro/primegit clone --depth 1 https://github.com/coleam00/context-engineering-introWhat 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.00605 |
| 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 3d 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.
This is a copy
89% identical to prime — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 3d ago First seen · 76 lines · 9 tokens per session scan A 52a0df58d48f
prime is a command published in the GitHub repository coleam00/context-engineering-intro (13,819 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 605 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to prime, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.