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.
npx agentmods add skills/p47phoenix/claude-plugins/flow-buildernpx skills add P47Phoenix/Claude-Plugins --skill flow-buildergit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWhat 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 | $0.00052 | $0.03795 |
| Opus 5 | $0.00026 | $0.01898 |
| Sonnet 5 | $0.00010 | $0.00759 |
| Haiku 4.5 | $0.00005 | $0.00380 |
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 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.
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:
- Long-horizon task planning - Complex goals requiring hierarchical decomposition
- Deterministic gating - Business rule-based decisions (not AI guesswork)
- Workflow orchestration - Coordinating multiple specialized agents
- Audit requirements - Complete traceability of decisions and outcomes
- 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
}
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.
- yesterday First seen · 563 lines · 52 tokens per session scan A a8c4961a97be
agentic-flow-builder is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 3,795 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.