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 skills add opencue/cuecards --skill agenticx-workflow-designergit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/skills/opencue/cuecards/agenticx-workflow-designer)<a href="https://agentmods.dev/skills/opencue/cuecards/agenticx-workflow-designer"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/agenticx-workflow-designer.svg" alt="Measured on agentmods" 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.00062 | $0.01006 |
| Opus 5 | $0.00031 | $0.00503 |
| Sonnet 5 | $0.00012 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
agenticx-workflow-designer 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 7d 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.
This is a copy
100% identical to agenticx-workflow-designer — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgenticX Workflow Designer
Guide for building workflows that orchestrate agents, tasks, and execution paths.
Core Components
| Component | Purpose |
|---|---|
Workflow |
Container for nodes and edges |
WorkflowNode |
A step in the workflow (agent + task) |
WorkflowEdge |
Connection between nodes (with optional conditions) |
WorkflowEngine |
Runtime executor for the workflow graph |
WorkflowGraph |
Graph representation of the workflow |
Basic Workflow
from agenticx import Workflow, WorkflowNode, WorkflowEdge
from agenticx.core import WorkflowEngine
# Define nodes
research_node = WorkflowNode(
id="research",
agent=researcher_agent,
task=research_task
)
analysis_node = WorkflowNode(
id="analysis",
agent=analyst_agent,
task=analysis_task
)
# Define edges (sequential flow)
edge = WorkflowEdge(source="research", target="analysis")
# Build workflow
workflow = Workflow(
id="research-pipeline",
nodes=[research_node, analysis_node],
edges=[edge]
)
# Execute
engine = WorkflowEngine()
result = engine.run(workflow)
CLI Workflow Creation
# Create workflow scaffold
agx workflow create research-pipeline --agents "researcher,analyst"
# List workflows
agx workflow list
# Run a workflow file
agx run workflows/research-pipeline.py --verbose
Workflow Patterns
Sequential Pipeline
Nodes execute one after another:
[Research] → [Analysis] → [Report]
edges = [
WorkflowEdge(source="research", target="analysis"),
WorkflowEdge(source="analysis", target="report"),
]
Parallel Execution
Multiple nodes execute concurrently:
┌→ [Web Search] ─┐
[Start] ─┤ ├→ [Merge]
└→ [DB Query] ─┘
edges = [
WorkflowEdge(source="start", target="web-search"),
WorkflowEdge(source="start", target="db-query"),
WorkflowEdge(source="web-search", target="merge"),
WorkflowEdge(source="db-query", target="merge"),
]
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.
- 7d ago First seen · 191 lines · 62 tokens per session scan A 23869781da9e
agenticx-workflow-designer is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,006 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agenticx-workflow-designer, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.
loongsuite-pilot-ops
Skill "loongsuite-pilot-ops" from alibaba/loongsuite-pilot, covering loongsuite-pilot-ops, quick start, todo: add quick start commands and usage.
atomic-visual-options
Planning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by…
atomic-wiki
Conversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the block in /.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via atomic wiki bucket add rather than a…
atomic-review
Compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", or invokes /atomic-review. Auto-triggers when reviewing pull requests.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…