workflow-orchestrator
Skill470 starsChanged 4 months agoMITView on GitHub
Module Loop and Iteration Skill for orchestrating multi-phase penetration testing workflows. Use when coordinating sequential tool execution, managing dependencies between reconnaissance and vulnerability scanning modules, implementing adaptive fallback strategies, or managing workflow state across iterations. Triggers on tasks requiring dependency chaining (e.g., Nmap results feeding into Nuclei), adaptive workflow adjustments based on results, or stateful iteration management to avoid redundant scans.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 231
Parallelization: Run independent modules concurrently
- Distinctive: line 232
Early Termination: Stop if critical finding detected
- Distinctive: line 233
Incremental Scans: Only test new paths in iterations
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workflow Orchestrator Skill
Manages cyclic testing workflows with dependency chaining, adaptive re-evaluation, and intelligent state management.
Quick Start
from scripts.workflow_engine import WorkflowEngine
from scripts.dependency_chain import DependencyChain
from scripts.state_manager import StateManager
# Initialize workflow
state = StateManager(target="example.com")
engine = WorkflowEngine(state)
# Define dependency chain
chain = DependencyChain()
chain.add_step("recon", NmapModule(), required=True)
chain.add_step("vuln_scan", NucleiModule(),
depends_on=["recon"],
input_mapper=lambda r: {"ports": r.open_ports})
chain.add_step("exploit", ExploitModule(),
depends_on=["vuln_scan"],
fallback=EnumModule()) # Fallback if no vulns
# Execute with iterations
results = await engine.execute(chain, max_iterations=3)Workflow Architecture
┌─────────────────────────────────────────────────────────────┐
│ WORKFLOW ITERATION │
├─────────────────────────────────────────────────────────────┤
│ 1. CHECK STATE → Skip if already tested │
│ 2. EXECUTE MODULE → Run with dependencies │
│ 3. EVALUATE RESULTS → Success / Empty / Error │
│ 4. ADAPT STRATEGY → Fallback if empty │
│ 5. CHAIN OUTPUTS → Feed into next modules │
│ 6. UPDATE STATE → Mark tested, store findings │
│ 7. ITERATE → Continue until max_iterations or complete │
└─────────────────────────────────────────────────────────────┘Core Components
1. Dependency Chaining (scripts/dependency_chain.py)
Manages execution order and data flow between modules:
chain = DependencyChain()
# Reconnaissance phase
chain.add_step("port_scan", NmapScanner(), required=True)
chain.add_step("service_enum", ServiceEnumerator(),
depends_on=["port_scan"])
# Vulnerability phase
chain.add_step("web_scan", NucleiScanner(),
depends_on=["port_scan"],
condition=lambda ctx: 80 in ctx.get("port_scan", {}).ports or
443 in ctx.get("port_scan", {}).ports)
# Exploitation phase
chain.add_step("sql_exploit", SQLMapModule(),
depends_on=["web_scan"],
condition=lambda ctx: "sql_injection" in ctx.findings)See references/dependency_patterns.md for complete patterns.
2. Adaptive Re-evaluation (scripts/adaptive_strategy.py)
Switches strategies based on results:
| Result | Action |
| Success | Continue to dependent modules |
| Empty | Trigger fallback module |
| Error | Retry with reduced intensity |
| Timeout | Queue for later retry |
# Define fallback strategies
fallbacks = {
"web_scan": {
"empty_result": "service_deep_scan",
"error": "reduced_web_scan",
"timeout": "queue_retry"
},
"vuln_scan": {
"empty_result": "full_port_scan",
"blocked": "stealth_scan"
}
}
strategy = AdaptiveStrategy(fallbacks)
new_module = strategy.decide("web_scan", result)3. State Management (scripts/state_manager.py)
Prevents redundant scans using Smart Memory:
state = StateManager(target="example.com")
# Check before scan
if state.is_tested("nmap", ports="80,443"):
return state.get_result("nmap")
# Execute and store
result = await nmap.scan("example.com", ports="80,443")
state.store("nmap", result, metadata={"ports": "80,443", "timestamp": now()})
# Track tested paths
state.add_tested_path("/admin", method="GET", params={"id": "1"})Workflow Patterns
Pattern 1: Standard Pentest Flow
Nmap (ports) → Nuclei (web vulns) → SQLMap (exploit) → Report
↓ ↓ (if empty) ↓
Service Fallback to: Fallback to:
Enum Dirbusting Manual checkPattern 2: Deep Dive Iteration
Iteration 1: Quick scan (top 100 ports)
Iteration 2: Full scan (all ports) - only if no services found
Iteration 3: Service-specific tools based on bannersPattern 3: Parallel Branches
┌→ Web Path (FFuF)
Nmap Ports ─┤
└→ Service Exploit (Metasploit)See references/workflow_templates/ for YAML definitions.
Integration with Zen-AI-Pentest
# Integration with ZenOrchestrator
from core.orchestrator import ZenOrchestrator
class WorkflowOrchestrator(ZenOrchestrator):
def __init__(self):
super().__init__()
self.workflow_engine = WorkflowEngine()
self.state_manager = StateManager()
async def run_workflow(self, target: str, strategy: str = "standard"):
# Load workflow template
template = WorkflowTemplate.load(f"assets/workflows/{strategy}.yaml")
# Initialize state
state = self.state_manager.for_target(target)
# Execute with iterations
return await self.workflow_engine.execute(
template=template,
state=state,
max_iterations=template.max_iterations
)State Storage Format
{
"target": "example.com",
"workflow_id": "uuid",
"iterations": [
{
"iteration": 1,
"modules": {
"nmap": {
"status": "completed",
"result_hash": "sha256:abc123",
"timestamp": "2026-03-20T14:46:00Z",
"inputs": {"ports": "top-100"},
"outputs": {"open_ports": [80, 443]}
},
"nuclei": {
"status": "completed",
"depends_on": ["nmap"],
"inputs": {"ports": [80, 443]}
}
}
}
],
"tested_paths": [
{"path": "/admin", "method": "GET", "params": {}},
{"path": "/api/users", "method": "POST", "params": {"id": "1"}}
],
"findings": ["CVE-2021-44228", "sql_injection_login"],
"adaptations": [
{"module": "web_scan", "trigger": "empty", "fallback": "dirbusting"}
]
}Error Handling
| Error Type | Handler | Action |
| Module Crash | Restart with reduced threads | Log, retry once |
| Dependency Missing | Skip dependent modules | Mark as blocked |
| State Corruption | Rebuild from last good | Alert operator |
| Max Iterations | Halt workflow | Return partial results |
Performance Optimization
- Caching: Store module results keyed by inputs
- Parallelization: Run independent modules concurrently
- Early Termination: Stop if critical finding detected
- Incremental Scans: Only test new paths in iterations
See references/optimization_guide.md.
References
- Dependency Patterns - Chaining strategies
- Workflow Templates - Pre-defined workflows
- State Machine - State transitions
- Optimization Guide - Performance tuning
Scripts
scripts/workflow_engine.py- Core workflow executionscripts/dependency_chain.py- Module dependency managementscripts/adaptive_strategy.py- Fallback and adaptation logicscripts/state_manager.py- Smart Memory integrationscripts/parallel_executor.py- Concurrent module execution
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- zhnnky329/MathModeling-skills★ 1.1ksame name
- jha0313/skills_repo★ 100same name
- jshsakura/awesome-opencode-skills★ 30same name
- imohammadfaraz/claude-skills-for-product-manager★ 19same name
- belokonm/claude-supercode-skills★ 11same name
- euCann/OSCAL-GRC-SKILLS★ 8same name
- k1lgor/virtual-company★ 4same name
- jha0313/agentic-workflow-eval-seminar★ 2same name
- GoogleMakesMeBetter/claude-skills-collection★ 1same name
- belentani7/claude-skills-pack★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- autonomous/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- poc-validatorSkill
- research-orchestratorSkill
- tdd-agentSkill
- ai-delegationSkill
- bash-automationSkill
- browser-automationSkill
- devops-cicdSkill
- devops-dockerSkill
- module-api-scannerSkill
- module-auth-bypass-moduleSkill
- module-beyondtrust-exploitSkill
- module-cert-transparencySkill
- module-cloud-scannerSkill
- module-command-injection-moduleSkill
- module-cve-databaseSkill
- module-cve-updaterSkill
- module-deserialization-moduleSkill
- module-dns-enumSkill
- module-email-harvesterSkill
- module-enhanced-reconSkill
- module-exploit-assistSkill
- module-ivanti-epmm-exploitSkill
- module-metadata-extractorSkill
- module-metasploit-integrationSkill
- module-nuclei-integrationSkill
- module-osintSkill
- module-osint-superSkill
- module-path-traversal-moduleSkill
- module-reconSkill
- module-report-exportSkill
- module-report-generatorSkill
- module-risk-scoringSkill
- module-searchsploit-integrationSkill
- module-service-vulnerability-mapperSkill
- module-siem-integrationSkill
- module-sql-injection-dbSkill
- module-sql-injection-moduleSkill
- module-ssrf-moduleSkill
- module-subdomain-scanner-advancedSkill
- module-subdomain-scannerSkill
- module-super-scannerSkill
- module-vuln-scannerSkill
- module-web-scraperSkill
- module-whois-lookupSkill
- module-windows-shell-bypassSkill
- module-wordlist-generatorSkill
- module-xss-moduleSkill
- module-xxe-moduleSkill
- module-zap-automationSkill
- module-zap-orchestratorSkill
- multi-languageSkill
- rag-vectorSkill
- security-reviewSkill
- .skillsSkill
- tool-aircrackSkill
- tool-amassSkill
- tool-bloodhoundSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

