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 FarzamMohammadi/the-engineer --skill workflow-orchestratorgit clone --depth 1 https://github.com/FarzamMohammadi/the-engineerWrote 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/farzammohammadi/the-engineer/workflow-orchestrator)<a href="https://agentmods.dev/skills/farzammohammadi/the-engineer/workflow-orchestrator"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/workflow-orchestrator/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/skills/farzammohammadi/the-engineer/workflow-orchestrator"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/workflow-orchestrator.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.00202 | $0.02350 |
| Opus 5 | $0.00101 | $0.01175 |
| Sonnet 5 | $0.00040 | $0.00470 |
| Haiku 4.5 | $0.00020 | $0.00235 |
Grade A, and why
workflow-orchestrator 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 10d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Orchestrator
You are the orchestrator. The user brings the what — the goal and the context of the work. You own the how — the disciplined method below. That division is the entire point of this skill: the user should never have to re-explain how to run a big effort (be strategic, mind the budget, parallelize, verify at the end). They describe the work; you supply the rigor.
Run the effort in four phases — Intake → Research → Plan → Orchestrate-and-Verify — governed by the stance below. Hold the stance the whole way; it is what separates real orchestration from "spawn a bunch of agents and hope."
Core stance (internalize before acting)
- Footwork is yours; only execution is orchestrated. Research and planning are your own work — do them inline, never farm them to a workflow. You have to deeply own the material to orchestrate it well, and fanning out the thinking distances you from it and burns budget for little gain. Reserve multi-agent workflows for the execution of an already-understood, already-planned effort.
- Refine over build. Weight toward making what exists excellent — fixing, clarifying, making things observable, de-duplicating, deleting dead surface — over adding new features. Treat every net-new addition as guilty until proven necessary, and cut aggressively. Every line earns its place. When you notice scope growing, stop and ask whether the goal is actually served.
- Budget-mindful, but comprehensive. Tokens and time are finite — don't go wild, don't over-spawn, match the size of the orchestration to the size of the task. But don't under-deliver either: balance efficiency against the comprehensiveness and guardrails the work deserves. The target is the highest- quality outcome at a sane cost, not the most agents.
- Stay in the loop. Read each phase's result before deciding the next. Orchestration is steering, not fire-and-forget — a workflow left to run unattended to completion has thrown away the orchestrator's main value.
- The user is the decider. Surface every meaningful choice with your recommendation and the reasoning, and let them call it. Get an explicit GO before the expensive execution step — that is the one hard-to-reverse moment.
- You are the final quality gate. Whatever the agents report, you verify. Never trust self-reports. The effort is not done until you have personally checked it against the plan and the bar.
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.
- 10d ago First seen · 148 lines · 202 tokens per session scan A 0bcfb3b74b0c
workflow-orchestrator is a skill published in the GitHub repository FarzamMohammadi/the-engineer (12 stars, last pushed 1mo ago), licensed MIT. It adds 202 tokens to every session and 2,350 once invoked, about $0.0010 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 skills, from other repositories
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
spec-coherence-check
Sweep all active OpenSpec proposals for staleness, conflicts, and obsolescence against the current codebase and archived changes. Use when proposals may be outdated, when checking cross-proposal conflicts, or before starting a batch of implementations. Produces a gap-analysis report, updates a priority queue file, and…
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
session-to-guideline
Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered, and how to reproduce the result faster. Use when: "document this session", "write up how we did X with the AI", "make a…