liteflow AGENTS.md

A set of instructions for coding agents working on LiteFlow, a Java framework for building business workflows from rules and components.

In plain words
What is it for?
Use it when compiling LiteFlow, running its full or targeted test suite, inspecting dependencies, or preparing a release build.
Why use it?
It lists the Maven commands and test options needed to build the whole project, one module, one test class, or one test method.

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/dromara/liteflow/agents-md
Clone the repo
git clone --depth 1 https://github.com/dromara/liteflow

Made for: Codex, OpenCode.

Per session 2,667 This file is loaded in full into every session.
When invoked 2,667 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.02667 $0.02667
Opus 5 $0.01333 $0.01333
Sonnet 5 $0.00533 $0.00533
Haiku 4.5 $0.00267 $0.00267

Measured yesterday against content hash 68ea36d4446d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

liteflow 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 yesterday.

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 · 247 lines

How it starts

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

AGENTS.md

This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.

Overview

LiteFlow (v2.16.1) is a lightweight rules engine framework for complex component-based business orchestration. It uses a DSL to drive workflows with support for hot reload and 11 scripting languages. The project targets Java 8+ (up to JDK 25) and has 2000+ test cases.

Official Documentation: https://liteflow.cc/pages/5816c5/

Commands

Build

# Build entire project (uses 'compile' profile by default, includes test modules)
mvn clean package -DskipTests

# Build with tests
mvn clean package

# Build specific module
mvn clean package -DskipTests -pl liteflow-core

# Build for release (production modules only, excludes tests)
mvn clean package -DskipTests -P release

Run Tests

# Run all tests
mvn test

# Run tests for specific module (30+ test modules in liteflow-testcase-el/)
mvn test -pl liteflow-testcase-el/liteflow-testcase-el-springboot

# Run single test class
mvn test -pl liteflow-core -Dtest=FlowExecutorTest

# Run specific test method
mvn test -pl liteflow-core -Dtest=FlowExecutorTest#testExecute

Other Commands

# Dependency tree
mvn dependency:tree

# View module structure
ls liteflow-*/pom.xml

High-Level Architecture

Core Execution Model

FlowExecutorChainCondition TreeNode Components

  1. FlowExecutor: Entry point for executing workflows (execute2Resp(chainId, param))
  2. FlowBus: Central metadata registry for all chains and nodes (thread-safe, supports hot reload)
  3. Chain: Named workflow composed of an EL expression that compiles to a Condition tree
  4. Slot/DataBus: Thread-safe context management using slot pooling (configurable slotSize)
  5. NodeComponent: Base class for all business logic components

Key Architectural Patterns

1. Two-Stage Parsing

Chains are built in two phases to handle circular dependencies:

  • Phase 1: Register chain IDs (creates placeholder chains)
  • Phase 2: Build complete condition trees with EL parsing

Read the full file on GitHub · 247 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. yesterday First seen · 247 lines · 2,667 tokens per session scan A 68ea36d4446d

Subscribe to this mod's changes

liteflow AGENTS.md is an instructions file published in the GitHub repository dromara/liteflow (3,837 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,667 tokens to every session, about $0.0133 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.