jnMetaCode/agency-orchestrator is a workflow system that lets people assemble teams of specialized AI roles from a natural-language request and run them against defined tasks and acceptance criteria. It is intended for individuals who want AI collaborators to produce research, content, products or other deliverables through web, desktop, Docker or command-line interfaces. The catalogue add-ons configure the agent roles and workflows used by the orchestrator.
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/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/windsurfrules)<a href="https://agentmods.dev/rules/jnmetacode/agency-orchestrator/windsurfrules"><img src="https://agentmods.dev/badge/rules/jnmetacode/agency-orchestrator/windsurfrules/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/jnmetacode/agency-orchestrator/windsurfrules"><img src="https://agentmods.dev/badge/rules/jnmetacode/agency-orchestrator/windsurfrules.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.00606 | $0.00606 |
| Opus 5.5 | $0.00242 | $0.00242 |
| Sonnet 5.5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
windsurfrules 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.
This is a copy
95% identical to workflow-runner — 5 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 — 51 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.
- 1mo ago First seen · 51 lines · 606 tokens per session scan A 9da397390927
windsurfrules is a cursor rule published in the GitHub repository jnMetaCode/agency-orchestrator (2,367 stars, last pushed 3d ago), licensed Apache-2.0. It adds 606 tokens to every session, about $0.0024 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to workflow-runner, differing in 5 lines, and is treated as a copy.
Other cursor rules, from other repositories
agents
A project rulebook that mirrors the instructions in AGENTS.md and points to the project's development, task-process, and architecture documents. It also identifies where the project's reusable skills are stored.
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.