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/base)<a href="https://agentmods.dev/rules/run-llama/flow-maker/base"><img src="https://agentmods.dev/badge/rules/run-llama/flow-maker/base/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/base"><img src="https://agentmods.dev/badge/rules/run-llama/flow-maker/base.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.00602 | $0.00602 |
| Opus 5.5 | $0.00241 | $0.00241 |
| Sonnet 5.5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
base 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Llama Agent Creator: Technical Details Supplement
This document supplements the main architecture.mdc file by providing specific details about the technologies and implementation of the Llama Agent Creator.
Application Stack
- Framework: Next.js
- Language: TypeScript
- UI Library: React with shadcn/ui components.
- Graph Visualization:
@xyflow/reactis used to build the interactive workflow editor inAgentFlow.tsx. - State & Storage:
- The visual graph's state (nodes and edges) is persisted to
localStorage. - Global chat state is managed via React Context in
src/components/ChatProvider.tsx.
- The visual graph's state (nodes and edges) is persisted to
- Core Workflow Engine:
@llamaindex/workflow-coreprovides the foundational classes and logic for creating and running workflows in the generated TypeScript code. - LLM Integrations: The application uses
@llamaindex/openai,@llamaindex/anthropic, and@llamaindex/googleto connect to various language models. - Testing: The project is set up with Vitest for testing.
File-Specific Details
This section clarifies the roles of key files and directories not fully detailed in the high-level architecture diagram.
-
app/api/: This directory contains the backend serverless functions that the interactive runner (RunView.tsx) calls. For instance, when apromptLLMnode is executed in the UI, it makes a POST request toapp/api/llm/call/route.tsto get the model's response. -
src/components/nodes/: This directory contains the React components for each type of node that can be dragged onto the canvas (e.g.,PromptLLMNode.tsx,DecisionNode.tsx,UserInputNode.tsx). These components define the appearance and configuration options of each node in the editor. -
src/components/CompileView.tsx: This component provides the user interface for triggering the TypeScript compilation and viewing/downloading the generated code.
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 · 39 lines · 602 tokens per session scan A 8848c913fed4
base is a cursor rule published in the GitHub repository run-llama/flow-maker (211 stars, last pushed 10mo ago), licensed MIT. It adds 602 tokens to every session, about $0.0024 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).