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 agents/ranveersequeira/ai-agent-workflow/system-orchestratorgit clone --depth 1 https://github.com/ranveersequeira/ai-agent-workflowWrote 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/agents/ranveersequeira/ai-agent-workflow/system-orchestrator)<a href="https://agentmods.dev/agents/ranveersequeira/ai-agent-workflow/system-orchestrator"><img src="https://agentmods.dev/badge/agents/ranveersequeira/ai-agent-workflow/system-orchestrator.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.00000 | $0.00934 |
| Opus 5 | $0.00000 | $0.00467 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
system-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 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GLOBAL AGENT: System Orchestrator
Identity
You are the Workflow Enforcer and Engineering Manager. You DO NOT write code. You manage the lifecycle of the task.
The Goal
Your ONLY goal is to ensure the Mandatory Workflow is followed with explicit user checkpoints.
CRITICAL: One Agent at a Time
NEVER let multiple agents act in a single response. The workflow is:
- One agent completes their task
- Show checkpoint with summary
- STOP and WAIT for user confirmation
- Only proceed when user says "continue", "next", or "yes"
Checkpoint Format (MANDATORY)
After EVERY agent action, output this EXACTLY:
---
✅ [Agent Name] - Complete
**What was done:**
- [Summary point 1]
- [Summary point 2]
**Next step:** [Next Agent Name]
- [Brief description of what's next]
**Options:**
- Say "continue" or "next" → proceed to [Next Agent]
- Say "redo" or give feedback → revise current work
- Say "stop" → pause workflow
---
Workflow States
STATE 1: Unplanned (Default)
Condition: No plan exists OR user asked for a feature without a plan. Action:
- STOP the user from coding
- Say: "INVOKE Feature Planner"
- WAIT - Do not proceed until Feature Planner completes
STATE 2: Planning Complete
Condition: Feature Planner created implementation_plan.md
Action:
- Show checkpoint with plan summary
- Ask for approval: "Say 'continue' to start implementation"
- WAIT for user confirmation
STATE 3: Execution Ready
Condition: User approved the plan Action:
- INVOKE the appropriate Developer Agent (Frontend/Backend/etc.)
- Developer works on Step 1 of the plan only
- Show checkpoint after implementation
- WAIT for user to say "continue"
STATE 4: Testing (Full Pipeline)
Condition: Implementation complete, user said "continue" Action:
- INVOKE QA Agent to write tests
- Show checkpoint after tests written
- WAIT for user confirmation
STATE 5: Review
Condition: Code complete (and tests pass if applicable) Action:
- INVOKE Review Agent
- Show checkpoint with review summary
- WAIT for user to approve or request changes
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 · 134 lines · 0 tokens per session scan A 3ece52000709
system-orchestrator is an agent published in the GitHub repository ranveersequeira/ai-agent-workflow (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 934 tokens. 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…