Skip to content

AnythingLLM AgentFlow Workflow Examples

github-actions[bot] edited this page Nov 15, 2026 · 1 revision

๐ŸŽฏ Purpose

Practical workflow examples showing how to chain AnythingLLM AgentFlows for complete security assessment sequences - from initial recon through email OSINT, breach checking, threat intel, and final report generation.

โš™๏ธ Function

Demonstrates multi-flow chains: DomainRecon -> EmailOSINT -> BreachChecker -> ThreatIntelCheck -> VulnReportGenerator. Includes example prompts, expected output structures, and guidance on passing data between flows.

๐Ÿ† Goal

Enable end-to-end automated security assessments using chained AgentFlows with minimal manual intervention between steps.

๐Ÿ“‹ When to Use

Planning an automated recon workflow; combining multiple flows for a comprehensive assessment; understanding how flows connect and hand off data to each other.

Overview

This document provides practical workflow examples using AnythingLLM custom AgentFlows for cybersecurity assessments and penetration testing. These workflows demonstrate how to chain together multiple flows to accomplish common security tasks efficiently.

Available AgentFlows

The following custom AgentFlows are referenced in these workflows:

  • CompanyOSINT - Gathers public information about target companies
  • DomainRecon - Performs comprehensive domain reconnaissance
  • EmailOSINT - Investigates email addresses and usernames across platforms
  • GitHubSecrets - Searches GitHub for exposed credentials and sensitive data
  • BreachChecker - Checks domains/emails against known data breaches
  • NmapAnalyzer - Analyzes Nmap scan results and provides recommendations
  • CVELookup - Retrieves CVE details and exploitability information
  • VulnReportGenerator - Creates professional vulnerability reports
  • ThreatIntelCheck - Checks IP/domain reputation against threat intelligence

Common Workflow Patterns

1. Pre-Engagement OSINT

Purpose: Gather intelligence before active testing begins

Workflow Steps:

  1. CompanyOSINT โ†’ Identify company structure, employee information, and email formats
    • Input: company_name, domain
  2. DomainRecon โ†’ Map attack surface and discover subdomains
    • Input: domain
  3. EmailOSINT โ†’ Investigate key personnel emails for breach history
    • Input: Key personnel emails from CompanyOSINT
  4. GitHubSecrets โ†’ Search for exposed credentials and secrets
    • Input: target_domain
  5. BreachChecker โ†’ Identify compromised accounts and leaked data
    • Input: domain

Output: Comprehensive pre-engagement intelligence report


2. Network Penetration Test

Purpose: Complete network security assessment workflow

Workflow Steps:

  1. Nmap Scan - Execute comprehensive port and service scan

    nmap -sV -sC -p- target.com -oN scan.txt
  2. NmapAnalyzer โ†’ Parse scan results and prioritize findings

    • Input: scan_results (from scan.txt), target_info
  3. CVELookup โ†’ Research each identified CVE

    • Input: cve_id, system_context
    • Repeat for each CVE discovered
  4. VulnReportGenerator โ†’ Document each finding professionally

    • Input: finding_title, finding_details, affected_systems, client_name
    • Repeat for each vulnerability
  5. Compile Final Report - Aggregate all findings into deliverable

Output: Professional penetration test report ready for client delivery


3. Incident Response

Purpose: Rapid investigation of security incidents

Workflow Steps:

  1. ThreatIntelCheck โ†’ Assess suspicious IP addresses

    • Input: Suspicious IP from logs/alerts
  2. DomainRecon โ†’ Investigate attacker domains

    • Input: Attacker domain (if identified)
  3. EmailOSINT โ†’ Research associated email addresses

    • Input: Email addresses from investigation
  4. BreachChecker โ†’ Identify compromised accounts

    • Input: Domain or email addresses

Output: Incident analysis with threat actor attribution and impact assessment


Quick Flow Combinations

Quick Vulnerability Assessment

Use Case: Fast initial security check

Nmap Scan
    โ†“
NmapAnalyzer (prioritize findings)
    โ†“
CVELookup (research critical CVEs)
    โ†“
VulnReportGenerator (document findings)

Deep OSINT Package

Use Case: Comprehensive intelligence gathering

CompanyOSINT (company intelligence)
    โ†“
EmailOSINT (key personnel investigation)
    โ†“
GitHubSecrets (credential exposure)
    โ†“
BreachChecker (breach history)

Network Mapping

Use Case: Attack surface enumeration

DomainRecon (discover assets)
    โ†“
Nmap Scan (active scanning)
    โ†“
ThreatIntelCheck (verify IPs)
    โ†“
NmapAnalyzer (analyze results)

Report Generation Sprint

Use Case: Batch document multiple findings

All vulnerability findings
    โ†“
VulnReportGenerator (repeat for each)
    โ†“
VulnReportGenerator (repeat for each)
    โ†“
VulnReportGenerator (repeat for each)
    โ†“
Compile into final report

General OSINT Assessment

Use Case: Standard reconnaissance workflow

Workflow Steps:

  1. CompanyOSINT โ†’ Determine email format and company structure
  2. EmailOSINT โ†’ Investigate key personnel emails for exposed data
  3. DomainRecon โ†’ Map complete attack surface including subdomains
  4. GitHubSecrets โ†’ Identify exposed credentials in public repositories

Output: Complete OSINT intelligence package


Usage Notes

Best Practices

  • Always ensure you have proper authorization before executing these workflows
  • Document each step as you progress through workflows
  • Use descriptive inputs for better analysis quality
  • Chain workflows based on findings from previous steps
  • Save outputs from each flow for final report compilation

Workflow Customization

These workflows can be:

  • Modified to suit specific engagement types
  • Combined for comprehensive assessments
  • Abbreviated for time-sensitive tasks
  • Extended with additional flows as needed

Tips for Effective Use

  1. Start broad, narrow down - Begin with OSINT, then focus on discovered assets
  2. Prioritize findings - Use NmapAnalyzer and CVELookup to identify critical issues first
  3. Document continuously - Run VulnReportGenerator for each finding immediately
  4. Verify results - Cross-reference flow outputs with manual testing
  5. Iterate as needed - Loop back through workflows when new information emerges

Example Complete Engagement

Scenario: External penetration test for Acme Corporation

Phase 1: Reconnaissance (Week 1)

CompanyOSINT โ†’ company: Acme Corporation, domain: acme.com
DomainRecon โ†’ domain: acme.com
GitHubSecrets โ†’ target: acme.com
BreachChecker โ†’ domain: acme.com
EmailOSINT โ†’ emails discovered from CompanyOSINT

Phase 2: Active Scanning (Week 2)

nmap -sV -sC -p- acme.com -oN acme-scan.txt
NmapAnalyzer โ†’ scan_results: acme-scan.txt
ThreatIntelCheck โ†’ IPs discovered from scan

Phase 3: Vulnerability Analysis (Week 2)

CVELookup โ†’ each CVE from NmapAnalyzer
Manual testing of discovered services
Additional targeted scans

Phase 4: Reporting (Week 3)

VulnReportGenerator โ†’ each finding documented
Compile all outputs into final report
Executive summary creation
Client presentation preparation

Document Version: 1.0
Last Updated: November 2025
Author: Pacific Northwest Computers
Purpose: AnythingLLM AgentFlow workflow reference guide

Related Files


๐Ÿ“„ Source: AI/AnythingLLM/anything_llm_agentflows.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Artificial Intelligence

Clone this wiki locally