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 ahmedibrahim085/Claude-Multi-Agent-Research-System-Skill --skill spec-workflow-orchestratorgit clone --depth 1 https://github.com/ahmedibrahim085/Claude-Multi-Agent-Research-System-SkillWrote 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/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-workflow-orchestrator)<a href="https://agentmods.dev/skills/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-workflow-orchestrator"><img src="https://agentmods.dev/badge/skills/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-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/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-workflow-orchestrator"><img src="https://agentmods.dev/badge/skills/ahmedibrahim085/claude-multi-agent-research-system-skill/spec-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.00039 | $0.15149 |
| Opus 5 | $0.00019 | $0.07574 |
| Sonnet 5 | $0.00008 | $0.03030 |
| Haiku 4.5 | $0.00004 | $0.01515 |
Grade A, and why
spec-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 11d 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 — 1,772 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Workflow Orchestrator
Table of Contents
- Purpose
- When to Use
- Orchestration Workflow
- Agent Roles
- Quality Gates
- File Organization
- Best Practices
- Examples
Purpose
Transform ideas into development-ready specifications through:
- Comprehensive planning with requirement analysis and architecture design
- Quality-gated iterative refinement of specifications
- Complete handoff documentation for development teams
- Orchestration across planning phase with 4 specialized agents
When to Use
Auto-invoke when user requests:
- Planning: "Plan [application]", "Design [system]", "Spec out [feature]", "Create requirements for [service]"
- Architecture: "Architecture for [project]", "Technical design for [application]", "Design specifications"
- Requirements: "Requirements for [project]", "Analyze requirements", "User stories for [feature]"
- Pre-Development: "Ready for development", "Spec-based planning", "Development specifications"
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 1,772 lines · 39 tokens per session scan A b01379b5ca5a
spec-workflow-orchestrator is a skill published in the GitHub repository ahmedibrahim085/Claude-Multi-Agent-Research-System-Skill (11 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 15,149 once invoked, about $0.0002 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
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
graph-engineering
Design multi-agent work as a dependency graph instead of a linear script — nodes, edges, fan-out/fan-in, verification gates, and mandatory per-node model/effort tiering. Use when designing or reviewing any multi-agent orchestration, workflow script, or parallel task decomposition. Also trigger when the user's prompt…
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.