WorkFlowX CLAUDE.md

A set of instructions for working on TreeX-X or WorkFlowX projects, including their CLAUDE.md project guidance. It explains how the main coding agent routes tasks, coordinates other agents, and follows repository-specific workflows.

In plain words
What is it for?
Following project instructions, choosing between xdo, xdel, and xflow workflows, coordinating implementation and evaluation, and handling repository file operations.
Why use it?
It gives the agent a consistent way to decide whether to work directly, delegate a task, or run a full planning and review process. This reduces confusion in projects with custom commands and constraints.

Instructions file

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/claude-md
Clone the repo
git clone --depth 1 https://github.com/TreeX-X/WorkFlowX
Per session 803 This file is loaded in full into every session.
When invoked 803 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.00803 $0.00803
Opus 5 $0.00402 $0.00402
Sonnet 5 $0.00161 $0.00161
Haiku 4.5 $0.00080 $0.00080

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

Security

Grade A, and why

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

CLAUDE.md · 62 lines

How it starts

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

CLAUDE.md - WorkflowX Instructions

You are the Main Agent. Responsibilities: direct execution, optional native parallel coordination, routing, design, and Hybrid Tree management when required.

Capabilities: native reasoning, optional Hybrid Tree management, and native Agent coordination.


Routing

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

Execution rule: xdo is direct work by the Main Agent and does not require a dispatch harness. Native parallel Agents are used only when the user explicitly requests parallel development. xdel delegates one Hybrid Tree task to coderX with self-review and no evaluatorX; xflow uses module 08 repository discovery, stage-batched socratesX clarification, and one Ready Summary confirmation before the full planning/evaluation workflow.

Routing and mode recommendation are defined in .claude/skills/orchestrateX/SKILL.md.


Orchestrator Workflow

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

Mode Command Behavior
xflow /xflow [-box] [-parallel] [-team] Full planning -> Hybrid Tree -> implementation -> evaluation
xdel /xdel <requirement or Hybrid Tree> Hybrid Tree-backed one-shot coderX delegation with self-review
xdo /xdo [--parallel] <requirement> Main Agent direct work; parallel only when explicitly requested

Agent dispatch:

Agent({ subagent_type: "coderX", isolation: "worktree", prompt: "<Dispatch Payload: coderX Task>" })
Agent({ subagent_type: "evaluatorX", isolation: "worktree", prompt: "..." })

Before dispatching coderX, Main Agent must assemble the Dispatch Payload: coderX Task defined in .claude/skills/orchestrateX/modules/02-bus-payload.md, including Execution Brief, Context Manifest, and Context Budget. Do not send vague implementation prompts to coderX.

Before dispatching evaluatorX, Main Agent must assemble the Dispatch Payload: evaluatorX Review Task defined in .claude/skills/orchestrateX/modules/02-bus-payload.md, including Review Brief, Review Context Manifest, and Review Context Budget. Do not send vague review prompts to evaluatorX.

Read the full file on GitHub · 62 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 · 62 lines · 803 tokens per session scan A 801fc721f9e6

Subscribe to this mod's changes

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