Borrowing it
Nothing to install: this file belongs to FarzamMohammadi/the-engineer. 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/FarzamMohammadi/the-engineer/main/AGENTS.mdgit clone --depth 1 https://github.com/FarzamMohammadi/the-engineerWrote 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/instructions/farzammohammadi/the-engineer/agents-md)<a href="https://agentmods.dev/instructions/farzammohammadi/the-engineer/agents-md"><img src="https://agentmods.dev/badge/instructions/farzammohammadi/the-engineer/agents-md.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.1 | $0.03170 | $0.03170 |
| Opus 5 | $0.01585 | $0.01585 |
| Sonnet 5 | $0.00634 | $0.00634 |
| Haiku 4.5 | $0.00317 | $0.00317 |
Grade A, and why
the-engineer AGENTS.md 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide
This is the entry point for any agent working on this project — regardless of provider, model, or tooling. Read this file first, every session.
The first section is the operational essentials: enough to land cold and act. Everything below the fold ("The Working Protocol") is how you actually work here — identity, context-loading discipline, and the checkpoints you must produce. Read the essentials to orient; read the protocol before you change anything.
Essentials
What this is. An autonomous orchestrator for AI coding agents. The Engineer runs as a long-lived daemon that listens for tasks, isolates each in a git worktree, and drives a coding CLI through the full engineering lifecycle (requirements → research → planning → execution → review → delivery). Three tiers: Core (the invariant brain), Adapters (stable contracts), Plugins (swappable implementations). See README.md for the full picture.
Key commands (full list in CONTRIBUTING.md):
pnpm dev <command> # Run the CLI in dev mode (no build/link) — e.g. pnpm dev doctor
pnpm test # Unit tests
pnpm test:all # All tiers (unit + integration + E2E)
pnpm run typecheck # tsc --noEmit (strict)
pnpm run lint # Biome + tsc + knip + madge
Project map:
| Path | What lives here |
|---|---|
src/core/ |
The invariant brain — EventBus, TaskEngine, Orchestrator, Daemon |
src/adapters/ |
Adapter base classes + SDK boundary (plugin authors import from here) |
src/plugins/ |
Plugin implementations, grouped by adapter type |
src/cli/ |
The engineer CLI (start, stop, status, logs, doctor, why, retry, rerun, cancel) |
src/schemas/ |
Centralized Zod schemas |
docs/ |
The system blueprint — architecture, plugins, configuration, CLI |
Configuring it without a TTY. If your task needs a running, configured daemon and you have no interactive terminal, use the non-interactive seed path — never the bare engineer start (it prompts):
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.
- 8d ago First seen · 203 lines · 3,170 tokens per session scan A 3bce90e6803d
the-engineer AGENTS.md is an instructions file published in the GitHub repository FarzamMohammadi/the-engineer (12 stars, last pushed 1mo ago), licensed MIT. It adds 3,170 tokens to every session, about $0.0158 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.