agentic-flow-builder

agentic-flow-builder is a skill for Claude Code, Codex from P47Phoenix/Claude-Plugins. It costs 52 tokens per session (3,795 once invoked), scanned A, original, MIT.

A guide for designing workflows where AI agents break down tasks, follow rules, remember context, and record decisions.

In plain words
What is it for?
Use it to plan multi-step agent tasks, route work between specialist agents, apply business rules at decision points, retain execution memory, and store records in SQLite.
Why use it?
It helps structure complex, long-running work when one AI response is not enough and decisions need predictable checks or an audit trail.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit Use it to plan multi-step agent tasks, route work between specialist agents, apply business rules at decision points, retain execution memory, and store records in SQLite.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/p47phoenix/claude-plugins/flow-builder
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.

Any agent
npx skills add P47Phoenix/Claude-Plugins --skill flow-builder
Clone the repo
git clone --depth 1 https://github.com/P47Phoenix/Claude-Plugins

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin agentic-flow-builder — /plugin install agentic-flow-builder after adding the marketplace above.

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

agentmods badge for agentic-flow-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/flow-builder/github.svg)](https://agentmods.dev/skills/p47phoenix/claude-plugins/flow-builder)
Your own site
<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/flow-builder"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/flow-builder/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.

agentmods 80×15 button for agentic-flow-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/flow-builder"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/flow-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,795 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00052 $0.03795
Opus 5.5 $0.00021 $0.01518
Sonnet 5.5 $0.00010 $0.00759
Haiku 4.5 $0.00005 $0.00380

Measured 1mo ago against content hash a8c4961a97be, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agentic-flow-builder 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.

agentic-flow-builder/skills/flow-builder/SKILL.md · 563 lines

How it starts

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

Agentic Flow Builder

This skill provides comprehensive guidance for building production-grade agentic flows that combine:

  • ReAcTree hierarchical agent tree decomposition for long-horizon task planning
  • Anthropic's workflow patterns for effective agent design
  • Business Rules Engine (BRE) for deterministic decision-making at gates
  • Dual memory system (episodic + working) for context management
  • SQLite persistence with full audit trails

Core Philosophy

Start simple, add complexity only when justified. Many problems can be solved with a single optimized LLM call. Only use agentic flows when the task requires:

  • Multi-step decomposition
  • Dynamic routing based on conditions
  • Iterative refinement
  • Complex orchestration across multiple specialized agents

When to Use Agentic Flows

Create an agentic flow when you need:

  1. Long-horizon task planning - Complex goals requiring hierarchical decomposition
  2. Deterministic gating - Business rule-based decisions (not AI guesswork)
  3. Workflow orchestration - Coordinating multiple specialized agents
  4. Audit requirements - Complete traceability of decisions and outcomes
  5. Memory across executions - Learning from past successful/failed attempts

Architecture Components

0. Dynamic Agent Assignment

The system automatically selects the best agent for each task based on:

  • Task description - Semantic matching with agent capabilities
  • Required tags - Specific skills needed (e.g., "code", "security", "data")
  • Agent type preference - General Claude models, Task agents, or External services
  • Performance history - Learns from past successes/failures

Agents are discovered dynamically:

  • Claude models (Sonnet, Opus, Haiku)
  • Claude Code Task agents (auto-discovered)
  • Custom plugin agents
  • External API services

Hot-reload support: New agents are automatically available without restarting.

Configuration example:

agent_node_config = {
    "goal": "Review code for security vulnerabilities",
    "required_tags": ["code", "security", "review"],
    "prefer_agent_type": "task",  # Prefer task agents if available
    "store_episodic": True  # Learn from this execution
}

Read the full file on GitHub · 563 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. 1mo ago First seen · 563 lines · 52 tokens per session scan A a8c4961a97be

Subscribe to this mod's changes

agentic-flow-builder is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 3,795 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens