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/commitgit 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.00007 | $0.00580 |
| Opus 5 | $0.00003 | $0.00290 |
| Sonnet 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 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.
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
100% identical to commit — 0 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 — 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 updatedCLAUDE.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.
- 2d ago First seen · 87 lines · 7 tokens per session scan A f98227f52ed9
commit is a command published in the GitHub repository coleam00/context-engineering-intro (13,813 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 580 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to commit, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.