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 rules/jnmetacode/agency-orchestrator/workflow-runnergit clone --depth 1 https://github.com/jnMetaCode/agency-orchestratorWrote 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/jnmetacode/agency-orchestrator/workflow-runner)<a href="https://agentmods.dev/rules/jnmetacode/agency-orchestrator/workflow-runner"><img src="https://agentmods.dev/badge/rules/jnmetacode/agency-orchestrator/workflow-runner.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 | $0.00013 | $0.00630 |
| Opus 5 | $0.00006 | $0.00315 |
| Sonnet 5 | $0.00003 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
workflow-runner 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 4d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Role Workflow Runner
When the user asks to run a workflow (YAML file) or a multi-role collaboration task, follow these steps:
1. Parse Workflow
Read the specified YAML file. Extract name, inputs, steps, depends_on, conditions, and loops.
2. Collect Inputs
required: trueinputs must be provided by the user- Optional inputs with
defaultuse the default value - Optional inputs without default are set to empty string
3. Build Execution Order
Topological sort by depends_on. Steps without dependencies belong to the same level and can run in parallel.
4. Execute Steps
For each step:
- Read
agency-agents-zh/{role}.md(search order: YAML's agents_dir → ./agency-agents-zh/ → ../agency-agents-zh/ → node_modules/agency-agents-zh/) - Extract all markdown content after the frontmatter (
---) as the role personality - Replace
{{variables}}in the task with context values (from inputs or previous step outputs) - Evaluate conditions: if
conditionis set, evaluate it. Skip the step if the condition is not met. Operators:contains,equals,not_contains,not_equals - Fully embody the role — use that role's expertise, frameworks, and communication style. Output should be substantive.
- Store the step's output text into the context variable (if step has an
outputfield) - Check loops: if
loopis set and exit_condition is not met, jump back toloop.back_tostep (max:loop.max_iterationsrounds)
Label each step: ### Step N/Total: step_id (Role Name)
5. Save Results
Save all outputs to files:
ao-output/{workflow-name}-{date}/
├── steps/
│ ├── 1-{step_id}.md
│ └── ...
├── summary.md # Final step's full output
└── metadata.json # Step states, timing, token counts
6. Suggest Iteration
After completion, always tell the user:
To improve a specific step, ask me to re-run from that step. I'll reuse all upstream outputs. For CLI:
ao run <workflow> --resume last --from <step-id>
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.
- 4d ago First seen · 56 lines · 13 tokens per session scan A 062cae52f5c7
workflow-runner is a cursor rule published in the GitHub repository jnMetaCode/agency-orchestrator (2,191 stars, last pushed 4d ago), licensed Apache-2.0. It adds 13 tokens to every session and 630 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
agents
Единые правила и скиллы проекта (зеркало AGENTS.md).
cursorrules
See CLAUDE.md for full context. Quick rules.
cursorrules
Robot control server. Do not move the physical robot without checking health first.
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.
cli-error-handling
CLI command error handling patterns.