engineer-flow: Instructions file for Codex

AGENTS.md

engineer-flow AGENTS.md is an instructions file for Codex, OpenCode from soden46/engineer-flow. It costs 587 tokens per session, scanned A, original, MIT.

A set of instructions for soden46/engineer-flow, an engineering workflow that routes tasks among general and specialist agent capabilities and performs a security check after development work.

In plain words
What is it for?
Use it to guide engineering-task routing, load project-specific instructions and memory when appropriate, coordinate up to two development specialists, and trigger post-development security verification.
Why use it?
It gives the agent rules for choosing relevant capabilities, managing project memory, and applying security review without relying on unrelated framework-specific instructions.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is soden46/engineer-flow's own configuration. It tells Codex and OpenCode how to work on engineer-flow itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything engineer-flow configures →

Reuse

Borrowing it

Nothing to install: this file belongs to soden46/engineer-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/soden46/engineer-flow/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/soden46/engineer-flow

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for engineer-flow AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/soden46/engineer-flow/agents-md/github.svg)](https://agentmods.dev/instructions/soden46/engineer-flow/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/soden46/engineer-flow/agents-md"><img src="https://agentmods.dev/badge/instructions/soden46/engineer-flow/agents-md/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.

agentmods 80×15 button for engineer-flow AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/soden46/engineer-flow/agents-md"><img src="https://agentmods.dev/badge/instructions/soden46/engineer-flow/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 587 This file is loaded in full into every session.
When invoked 587 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00587 $0.00587
Opus 5.5 $0.00235 $0.00235
Sonnet 5.5 $0.00117 $0.00117
Haiku 4.5 $0.00059 $0.00059

Measured 1mo ago against content hash feb3295fa4ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

engineer-flow 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 1mo 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.

AGENTS.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Engineer Flow Agent Instructions

Use skills/engineer-flow/SKILL.md as the canonical entrypoint for engineering tasks.

Runtime Model

Engineer Flow consists of:

  • one public engineer-flow Agent Skill
  • 16 generalized internal engineering capabilities under skills/engineer-flow/core/
  • conditional persistent project memory under skills/engineer-flow/infrastructure/memory-management/
  • compatible user-installed external Agent Skills
  • sparse specialist routing with at most 2 development specialists
  • mandatory post-development security verification

Framework-specific and technology-specific expertise should come from project evidence, native stack mechanisms, or relevant external Agent Skills.

Do not add built-in framework adapters.

Routing Rules

  • Start from the engineering concern, not the framework.
  • Select at most 2 development specialists:
    • primary
    • optional support
  • Prefer generalized internal capabilities for generic engineering tasks.
  • Activate external skills only when task or project evidence specifically supports them.
  • Do not activate unrelated external skills because of generic keyword overlap.
  • Current project code and configuration take precedence over assumptions.
  • Prefer the smallest correct change.
  • Preserve existing project conventions where reasonable.
  • Avoid unnecessary repository-wide exploration.

Memory Contract

Memory is conditional infrastructure and never consumes a primary or support specialist slot.

Use memory preflight only when prior project/session/workflow context could materially affect correctness.

Prefer a host-provided MCP memory tool when available. Otherwise use:

skills/engineer-flow/infrastructure/memory-management/scripts/memory.mjs

Current code and configuration override stale memory.

Checkpoint only durable reusable project knowledge and never store secrets, credentials, .env values, raw tokens, or personal data.

Security Contract

After development, run the mandatory security verification stage.

Read the full file on GitHub · 108 lines

Changes

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.

  1. 1mo ago First seen · 108 lines · 587 tokens per session scan A feb3295fa4ad

Subscribe to this mod's changes

engineer-flow AGENTS.md is an instructions file published in the GitHub repository soden46/engineer-flow (3 stars, last pushed 1mo ago), licensed MIT. It adds 587 tokens to every session, about $0.0023 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-31.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,384 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens