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.
git clone --depth 1 https://github.com/run-llama/flow-makerWrote 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.
[](https://agentmods.dev/rules/run-llama/flow-maker/llamaindex)<a href="https://agentmods.dev/rules/run-llama/flow-maker/llamaindex"><img src="https://agentmods.dev/badge/rules/run-llama/flow-maker/llamaindex/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.
<a href="https://agentmods.dev/rules/run-llama/flow-maker/llamaindex"><img src="https://agentmods.dev/badge/rules/run-llama/flow-maker/llamaindex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01041 | $0.01041 |
| Opus 5.5 | $0.00416 | $0.00416 |
| Sonnet 5.5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
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 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.
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.
-
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.
-
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 functionhandlerFnto be called when any of the specifiedeventsare detected.
-
Asynchronous by Design: All handlers can be
asyncand are expected to returnPromises, 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.
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.
- 1mo ago First seen · 95 lines · 1,041 tokens per session scan A c347196a0a2d
llamaindex is a cursor rule published in the GitHub repository run-llama/flow-maker (211 stars, last pushed 10mo ago), licensed MIT. It adds 1,041 tokens to every session, about $0.0042 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).