llamaindex

Reference material for the TypeScript workflow-core library from LlamaIndex. It explains workflows built from events and handler functions, including asynchronous execution.

In plain words
What is it for?
Use it when generating or maintaining TypeScript agent scripts that define events, register handlers, and connect asynchronous workflow steps.
Why use it?
It helps an agent understand how these event-driven workflows are structured and how one handler leads to the next.

Cursor rule for Cursor

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 rules/run-llama/flow-maker/llamaindex
Clone the repo
git clone --depth 1 https://github.com/run-llama/flow-maker

Made for: Cursor.

Per session 1,041 This file is loaded in full into every session.
When invoked 1,041 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.01041 $0.01041
Opus 5 $0.00521 $0.00521
Sonnet 5 $0.00208 $0.00208
Haiku 4.5 $0.00104 $0.00104

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

Security

Grade A, and why

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

.cursor/rules/llamaindex.mdc · 95 lines

How it starts

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

Understanding @llamaindex/workflow-core (TypeScript)

This document explains the core concepts of the @llamaindex/workflow-core library for TypeScript, which is used by typescript-compiler.ts to generate executable agent scripts. The library uses a functional, event-driven paradigm.

Core Concepts

The workflow is built by defining events and then creating handlers that listen for those events. The execution flow is determined by which events are emitted from handlers.

  1. Event-Driven Flow: The entire workflow is orchestrated by events. A handler function executes when it receives an event of a type it's registered to handle. After executing its logic, the handler can emit a new event, which in turn triggers another handler.

  2. Functional Approach: Instead of class-based inheritance (like in Python), the TypeScript version uses factory functions to build the workflow.

    • workflowEvent<T>(): Creates a new type of event.
    • createWorkflow(): Creates a new workflow instance.
    • workflow.handle([...events], handlerFn): Registers a function handlerFn to be called when any of the specified events are detected.
  3. Asynchronous by Design: All handlers can be async and are expected to return Promises, making them suitable for I/O-bound tasks like LLM calls and tool interactions.

Key Components

1. workflowEvent

This function is used to define the different types of events that will flow through your system. They are the data carriers.

import { workflowEvent } from "@llamaindex/workflow-core";

// Define an event that carries a string payload
const startEvent = workflowEvent<string>();

// Define an event that carries a structured object
interface ToolCall {
  id: string;
  name: string;
  args: any;
}
const toolCallEvent = workflowEvent<ToolCall>();

2. createWorkflow and .handle

createWorkflow() creates the main workflow object. The .handle() method is then used to register listeners for specific events. The return value of a handler function becomes a new event that is dispatched into the workflow.

Read the full file on GitHub · 95 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 · 95 lines · 1,041 tokens per session scan A c347196a0a2d

Subscribe to this mod's changes

llamaindex is a cursor rule published in the GitHub repository run-llama/flow-maker (211 stars, last pushed 8mo ago), licensed MIT. It adds 1,041 tokens to every session, about $0.0052 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.