Skip to content

Fully autonomous AI Agents system capable of performing complex penetration testing tasks

Apply suggestions from code review

Dmitry Ngde6f527e6f4f
diff --git a/backend/docs/prompt_engineering_pentagi.md b/backend/docs/prompt_engineering_pentagi.md
index 7cbf52e4..e2d8ed74 100644
--- a/backend/docs/prompt_engineering_pentagi.md
+++ b/backend/docs/prompt_engineering_pentagi.md
@@ -94,7 +94,7 @@ A comprehensive framework for designing high-performance prompts within the Pent
**Security and Operational Boundaries**
- Explicitly state the **scope** of permitted actions and **security constraints**. Reference `security-tools.mdc` for general tool security context.
-- For engagement-level boundaries, start from the reusable [scope-of-work pentest prompt template](../../examples/prompts/scope_of_work_pentest.md) and adapt the allowed targets, denied targets, stop conditions, and evidence expectations before the flow starts.
+- For engagement-level boundaries, start from the reusable [scope-of-work pentest prompt template](../../examples/prompts/scope_of_work_pentest.md) and adapt the allowed targets, out-of-scope targets, stop conditions, and evidence expectations before the flow starts.
- Define **Docker container limitations** within `<container_constraints>`, populated by template variables like `{{.DockerImage}}`, `{{.Cwd}}`, `{{.ContainerPorts}}`. Specify restrictions clearly (e.g., "No direct host access," "No GUI applications," "No UDP scanning").
- Specify **forbidden actions** clearly. Use **ALL CAPS** for critical security warnings, permissions, or prohibitions (e.g., "DO NOT attempt to install new software packages," "ONLY execute commands related to the current SubTask").
- Emphasize working **strictly within the scope of the current `SubTask`**. The agent must understand its current objective based on `{{.ExecutionContext}}` and not attempt actions related to other SubTasks or the overall Flow goal unless explicitly instructed within the current SubTask. Reference `data-models.mdc` and `controller.md` for task/subtask relationships.
diff --git a/examples/prompts/scope_of_work_pentest.md b/examples/prompts/scope_of_work_pentest.md
index dd813664..86cdd1f6 100644
--- a/examples/prompts/scope_of_work_pentest.md
+++ b/examples/prompts/scope_of_work_pentest.md
@@ -80,7 +80,7 @@ Before every network action, command, script, scan, exploit attempt, or generate
The same structure can later be converted into backend validation rules:
-- Store allowed targets and denied targets as normalized host, URL, IP, and CIDR entries.
+- Store allowed targets and out-of-scope targets as normalized host, URL, IP, and CIDR entries.
- Validate command arguments before execution for tools that expose target flags or positional targets.
- Require a per-tool policy for mass scanners, web fuzzers, exploit frameworks, and generated scripts because each expands targets differently.
- Treat ambiguous destinations as blocked until a user or maintainer-approved policy resolves them.