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/savagelysubtle/BIG-BRAIN-Memory-BankWrote 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/savagelysubtle/big-brain-memory-bank/160-workflow-orchestration)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/160-workflow-orchestration"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/160-workflow-orchestration/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/savagelysubtle/big-brain-memory-bank/160-workflow-orchestration"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/160-workflow-orchestration.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.04188 | $0.04188 |
| Opus 5 | $0.02094 | $0.02094 |
| Sonnet 5 | $0.00838 | $0.00838 |
| Haiku 4.5 | $0.00419 | $0.00419 |
Grade A, and why
160-workflow-orchestration 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 8d 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 — 629 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TL;DR: The Workflow Orchestration system manages operational workflows throughout task execution, coordinating task phases, maintaining state, and ensuring appropriate process application based on task requirements.
1.0.0
1. **Plan Workflow**
- Purpose: Architecture, design, and planning activities
- Focus: Understanding requirements, exploring options, designing solutions
- Process: Analysis, design alternatives, evaluation, selection, planning
- Outputs: Design documents, architecture decisions, implementation plans
2. **Act Workflow**
- Purpose: Implementation and execution activities
- Focus: Building, testing, refining implementations
- Process: Component building, testing, debugging, documentation
- Outputs: Functional code, tests, implementation documentation
3. **Review Workflow**
- Purpose: Evaluation and verification activities
- Focus: Assessing quality, correctness, alignment
- Process: Inspection, testing, validation, feedback
- Outputs: Quality assessments, issue reports, improvement recommendations
4. **Hybrid Workflow**
- Purpose: Combined planning and implementation
- Focus: Iterative development with ongoing design
- Process: Interwoven planning and implementation
- Outputs: Progressive implementation with evolving design
Each workflow type has specialized processes and outputs.
1. **Task Nature Assessment**
- Planning tasks → Plan workflow
- Implementation tasks → Act workflow
- Evaluation tasks → Review workflow
- Balanced tasks → Hybrid workflow
2. **Task Characteristics**
- High uncertainty → Plan-heavy workflows
- Clear requirements → Act-heavy workflows
- Quality-critical → Review-intensive workflows
- Experimental → Design-implement iterations
3. **Contextual Factors**
- Project stage influences selection
- Previous work determines appropriate continuation
- Risk level affects workflow rigor
- Time constraints impact workflow scope
4. **Complexity Influence**
- Higher complexity → More structured workflows
- Lower complexity → Streamlined workflows
- Critical tasks → Enhanced validation steps
- Routine tasks → Standardized processes
Selection ensures the most appropriate workflow for each task context.
1. **Context Analysis**
- Review existing system understanding
- Clarify requirements and constraints
- Identify stakeholders and concerns
- Establish success criteria
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.
- 8d ago First seen · 629 lines · 4,188 tokens per session scan A 4443c5742759
160-workflow-orchestration is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It adds 4,188 tokens to every session, about $0.0209 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 cursor rules, from other repositories
wrapup
End-of-session wrap-up: summarizes the session and pushes a log to the project's linked NotebookLM notebook. Activate with @wrapup in chat, or "wrap up", "save this session", or "end of session".
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
search-routing
Smart Search Routing — always use QMD semantic search when available, never bypass with grep for vault content.
composer-coding-excellence
Coding craft — surgical edits, convention matching, no scope creep, no slop comments, no fabricated APIs.
clarify-first
Infer-and-act by default — ask only on high confusion weight, after inspecting, with a decision-linked question.
composer-debugging
Root-cause debugging — reproduce, trace data flow, test cheapest hypothesis, fix the cause not the symptom.