autonomous-loops

name	autonomous-loops
description	Performing repetitive enumeration across many targets - Running batch vulnerability scans on multiple hosts - Monitoring for changes in target environment - Executing attack chains that require iterative steps - User says "loop", "automate", "batch", "repeat.
origin	openclaw
version	0.2.0.2
compatibility	["openclaw","claude-code","cursor","windsurf"]
allowed-tools	["Bash","Read","Write","Edit","WebSearch","WebFetch","Agent"]
defense_triple_required	false
metadata	{"domain":"infrastructure","tool_count":0,"guide_count":8,"last_reviewed":"2026-07-26"}

Autonomous Loops

Supplementary Files:

• payloads.md — Scope Lock templates, rate limit configurations, loop command templates, and error handling response templates
• test-cases.md — Structured test cases for sequential pipeline, watch loop, batch processing, learning cycle, scope violation, and rate limit backoff
• guides/safe-autonomous-pentest.md — Deep-dive guide on autonomous vs manual decision making, scope lock construction, loop composition, and monitoring

Summary

Autonomous Loops skill domain covering infrastructure operations.

Domain: infrastructure

Use Cases

1. Sequential Pipeline — Chain multiple security tools in order (recon → scan → exploit) with automatic phase transitions
2. Watch Loop — Monitor a target for changes (new ports, updated services) over extended periods
3. Batch Processing — Run the same test against multiple targets with rate limiting and error recovery
4. Learning Cycle — Execute a skill, capture results, extract patterns, and update knowledge base automatically
5. Scope-Locked Automation — Run autonomous loops with hard boundaries that prevent actions outside authorized scope

Activation

• Performing repetitive enumeration across many targets
• Running batch vulnerability scans on multiple hosts
• Monitoring for changes in target environment
• Executing attack chains that require iterative steps
• User says "loop", "automate", "batch", "repeat", "iterate"

Core Principle

Autonomous does not mean uncontrolled. Every loop must have:

1. A defined scope (what it can and cannot touch)
2. A termination condition (when it stops)
3. Rate limiting (how fast it runs)
4. Evidence logging (what it did)
5. Error handling (what happens when things go wrong)

Four Loop Patterns

Pattern 1: Sequential Pipeline

Execute a sequence of steps across multiple targets, one at a time.

FOR EACH target IN target_list:
    IF scope_check(target) == ALLOWED:
        result = execute_step(target)
        log_evidence(target, result)
        IF result.status == FAIL:
            handle_error(target, result)
            CONTINUE or BREAK based on severity
    ELSE:
        log_skipped(target, "Out of scope")