WorkFlowX AGENTS.md

A project instruction file for WorkflowX that explains how Codex should route work, use project-specific agents, and run workflow commands. It also describes how delegated coding and evaluation tasks must be reported and verified.

In plain words
What is it for?
Use it when running WorkflowX commands, choosing between available subagents, reading project configuration, or handling degraded delegation.
Why use it?
It prevents the coding assistant from pretending to have delegated work when no subagent is available and keeps workflow state consistent.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/treex-x/workflowx/agents-md
Clone the repo
git clone --depth 1 https://github.com/TreeX-X/WorkFlowX

Made for: Codex, OpenCode.

Per session 887 This file is loaded in full into every session.
When invoked 887 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00887 $0.00887
Opus 5 $0.00443 $0.00443
Sonnet 5 $0.00177 $0.00177
Haiku 4.5 $0.00089 $0.00089

Measured 2d ago against content hash d3be83854224, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 64 lines

How it starts

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

AGENTS.md - WorkflowX Codex Instructions

This file is the Codex entry instruction for WorkflowX.

Codex runtime truth lives in this file, .codex/config.toml, .codex/skills/, and .codex/agents/.


Routing

Full specification: .codex/skills/orchestrateX/SKILL.md

Codex uses project subagent definitions from .codex/agents/. The Main Agent owns direct execution and may use native parallel Agents when the user explicitly requests parallel work. xdel/xflow may use the corresponding workflow agents when their mode requires it.

Subagent dispatch follows .codex/skills/orchestrateX/modules/09-dispatch-adapter.md: use a native Agent/subagent tool when one is exposed; otherwise use Codex prompt-spawn when the current surface supports prompt-triggered subagents; otherwise report dispatch as degraded. Do not silently pretend to be coderX / evaluatorX in the main-agent context.

When using prompt-spawn dispatch, Main Agent must emit the WorkflowX Subagent Spawn Request envelope from module 09 and require the returned WorkflowX Subagent Receipt before accepting the output as a verified subagent result.

Before automatically dispatching coderX, Main Agent must assemble a Dispatch Payload: coderX Task as defined in .codex/skills/orchestrateX/modules/02-bus-payload.md. The payload must state mode, dispatch type, objective, requirement source, Execution Brief, Context Manifest, Context Budget, scope, forbidden files, required skills, output contract, verification requirements, and stop conditions. Do not send vague implementation prompts to coderX.

Before automatically dispatching evaluatorX, Main Agent must assemble a Dispatch Payload: evaluatorX Review Task as defined in .codex/skills/orchestrateX/modules/02-bus-payload.md. The payload must state evaluation type, Review Brief, Review Context Manifest, Review Context Budget, changed files, affected ACs, review focus, output contract, and expansion rules. Do not send vague review prompts to evaluatorX.

Read the full file on GitHub · 64 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. 2d ago First seen · 64 lines · 887 tokens per session scan A d3be83854224

Subscribe to this mod's changes

WorkFlowX AGENTS.md is an instructions file published in the GitHub repository TreeX-X/WorkFlowX (55 stars, last pushed 2d ago), licensed MIT. It adds 887 tokens to every session, about $0.0044 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.

Related

Other instructions, from other repositories