ai-delegation
Skill470 starsChanged 4 months agoMITView on GitHub
Workflows für Agent-to-Agent Delegation, Workflow-Chaining, Sub-Agent-Spawning, Result-Merging. Zwischen Agenten wird Kontext über JSON weitergegeben:
Files
AI↔AI Delegation & Multi-Agent Orchestrierung Skill
Workflows für Agent-to-Agent Delegation, Workflow-Chaining, Sub-Agent-Spawning, Result-Merging.
Architektur
User Request
│
▼
Orchestrator Agent (Coordinator)
│
├── ▶ Specialist Agent A ──▶ Result
├── ▶ Specialist Agent B ──▶ Result
└── ▶ Specialist Agent C ──▶ Result
│
▼
Merge & Final ResponseDelegation Patterns
1. Sequential Chain
Jeder Agent baut auf dem vorherigen auf:
deep-recon --target example.com → recon.json
deep-exploit --target-file recon.json → exploit.log
deep-report --scan-id <id> --format pdf → report.pdf2. Parallel Fan-Out
Mehrere Agenten gleichzeitig, Ergebnisse mergen:
import asyncio
async def fan_out(target: str):
tasks = [
agent_run("recon", target),
agent_run("network", target),
agent_run("cloud", target),
agent_run("social", target),
]
results = await asyncio.gather(*tasks, return_exceptions=True)
return merge_results(results)3. Hierarchisch (Manager + Worker)
manager_prompt = """
Analyze the task and break it into sub-tasks.
Assign each to the right specialist agent.
Track dependencies and merge results.
"""4. ReAct mit Sub-Agent-Calls
class DelegatingReActAgent(ReActAgent):
async def _act(self, plan: str) -> ToolResult:
if plan.get("delegate_to"):
# Spawn sub-agent
sub = create_agent(plan["delegate_to"])
return await sub.run(plan["task"])
return await super()._act(plan)Workflow Chaining
Dependency Graph
workflow = coordinator.create_workflow(
target="example.com",
phases=["recon", "scan", "exploit", "report"],
)
# Automatisch: recon-output → scan-input, scan-output → exploit-inputConditional Branching
if result["critical_findings"] > 0:
# Escalate to red team
workflow.add_phase("redteam")
else:
# Skip to report
workflow.add_phase("report")Context Passing
Zwischen Agenten wird Kontext über JSON weitergegeben:
{
"task_id": "wf-abc123",
"target": "example.com",
"phase": "recon",
"results": {
"subdomains": ["admin.example.com", "api.example.com"],
"ports": {"22": "open", "80": "open", "443": "open"},
"technologies": ["nginx", "react", "postgresql"]
},
"artifacts": ["recon.json", "screenshots/"]
}Hermes Integration (via MCP)
# Agent delegiert an anderen Agent
zen_agents_agent_run(agent_type="recon", target="example.com")
# → Result enthält findings für nächsten Agent
# Workflow orchestrieren
zen_agents_workflow_create(target="example.com", phases="recon,scan,exploit,report")Fehlerbehandlung
class AgentOrchestrator:
def handle_failure(self, agent: str, error: str):
if "timeout" in error.lower():
return self.retry(agent, timeout=timeout * 2)
elif "rate_limit" in error.lower():
ks_rotate_now() # VPN-Killswitch
return self.retry(agent)
else:
return self.escalate(agent, error)In this repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- autonomous/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- poc-validatorSkill
- workflow-orchestratorSkill
- research-orchestratorSkill
- tdd-agentSkill
- 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.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

