Fully autonomous AI Agents system capable of performing complex penetration testing tasks
Go ai-agentsai-security-toolanthropicautonomous-agentsgolanggptgraphqlmulti-agent-systemoffensive-securityopen-sourceopenaipenetration-testingpenetration-testing-toolsreactsecurity-automationsecurity-testingsecurity-toolsself-hosted
docs: reorganize Pentesting Prompt Methodology section in README.md
Dmitry Ngb748af537481
diff --git a/README.md b/README.mdindex 38a8bf44..cb0cb98c 100644--- a/README.md+++ b/README.md@@ -41,7 +41,6 @@- [Docker Image Configuration](#docker-image-configuration)- [Development](#development)- [Testing LLM Agents](#testing-llm-agents)- - [Pentesting Prompt Methodology](#pentesting-prompt-methodology)- [Embedding Configuration and Testing](#embedding-configuration-and-testing)- [Function Testing with ftester](#function-testing-with-ftester)- [Building](#building)@@ -3309,18 +3308,6 @@ When developing new prompt templates or agent behaviors:3. Observe responses and adjust prompts accordingly4. Check Langfuse for detailed traces of all function calls-### Pentesting Prompt Methodology--When refining prompts for offensive security work, give the agent a clear methodology instead of a flat list of payloads:--1. Start with explicit scope, authorization, and success criteria-2. Map the application first: roles, routes, parameters, uploads, integrations, and trust boundaries-3. Prioritize attack surfaces systematically instead of testing everything at once-4. Validate findings with reproducible evidence before escalating to deeper exploitation-5. Finish with report-ready notes that capture impact, prerequisites, and next steps--For PentAGI-specific prompt guidance, see [`backend/docs/prompt_engineering_pentagi.md`](backend/docs/prompt_engineering_pentagi.md). For a practical starting point, reuse and adapt [`examples/prompts/base_web_pentest.md`](examples/prompts/base_web_pentest.md) to match the target application, technology stack, and engagement scope.-### Verifying Docker Container SetupEnsure containers are properly configured:@@ -3378,6 +3365,18 @@ The main utility accepts several options:Function-specific arguments are passed after the function name using `-name value` format.+### Pentesting Prompt Methodology++When refining prompts for offensive security work, give the agent a clear methodology instead of a flat list of payloads:++1. Start with explicit scope, authorization, and success criteria+2. Map the application first: roles, routes, parameters, uploads, integrations, and trust boundaries+3. Prioritize attack surfaces systematically instead of testing everything at once+4. Validate findings with reproducible evidence before escalating to deeper exploitation+5. Finish with report-ready notes that capture impact, prerequisites, and next steps++For PentAGI-specific prompt guidance, see [`backend/docs/prompt_engineering_pentagi.md`](backend/docs/prompt_engineering_pentagi.md). For a practical starting point, reuse and adapt [`examples/prompts/base_web_pentest.md`](examples/prompts/base_web_pentest.md) to match the target application, technology stack, and engagement scope.+## Building### Building Docker Image