vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-21 08:15:23 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[PR #266] [MERGED] docs: add pentesting prompt methodology guidance #280

New Issue
Closed
opened 2026-06-06 22:10:01 -04:00 by yindo · 0 comments
yindo commented 2026-06-06 22:10:01 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/vxcontrol/pentagi/pull/266
Author: @mason5052
Created: 4/15/2026
Status: ✅ Merged
Merged: 4/22/2026
Merged by: @asdek

Base: feature/next-release ← Head: codex/issue-79-pentest-methodology-guide

📝 Commits (2)

  • a9a0b76 docs: add pentesting prompt methodology guide
  • c893bb8 docs: fix pentesting methodology links

📊 Changes

2 files changed (+27 additions, -0 deletions)

View changed files

📝 README.md (+13 -0)
📝 backend/docs/prompt_engineering_pentagi.md (+14 -0)

📄 Description

Summary

  • add a pentesting prompt methodology section to the README for prompt authors
  • expand the prompt engineering guide with a pentester-specific methodology checklist and reference material
  • point contributors to the existing examples/prompts/base_web_pentest.md starter prompt

Problem

Issue #79 asks for better guidance on how AI prompts should approach pentesting. PentAGI already includes prompt templates and a sample web pentest prompt, but the documentation does not explain how to translate pentesting methodology into reusable agent guidance.

Solution

  • add a new README section under Development that describes a phase-based prompt methodology for offensive security work
  • extend backend/docs/prompt_engineering_pentagi.md with guidance for authorization boundaries, coverage-first mapping, attack-surface prioritization, low-risk validation, evidence capture, iterative memory use, and report-ready summaries
  • reference public methodology sources such as HackTricks and Pentest Book as inspiration without copying large external checklists into PentAGI's prompt docs

User Impact

Prompt authors now have a clearer path for turning pentest methodology into PentAGI prompts. This should make new prompt iterations easier to structure, easier to review, and easier to adapt to different engagement scopes.

Test Plan

  • confirm the new README section is linked from the table of contents
  • verify the documentation references existing PentAGI prompt assets and external methodology sources accurately
  • run git diff --check

Closes #79

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/vxcontrol/pentagi/pull/266 **Author:** [@mason5052](https://github.com/mason5052) **Created:** 4/15/2026 **Status:** ✅ Merged **Merged:** 4/22/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `feature/next-release` ← **Head:** `codex/issue-79-pentest-methodology-guide` --- ### 📝 Commits (2) - [`a9a0b76`](https://github.com/vxcontrol/pentagi/commit/a9a0b76226d3f8e0b41fe44c1d1333df3df6c152) docs: add pentesting prompt methodology guide - [`c893bb8`](https://github.com/vxcontrol/pentagi/commit/c893bb817e996328a30f66e2ceeccdda983530f6) docs: fix pentesting methodology links ### 📊 Changes **2 files changed** (+27 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+13 -0) 📝 `backend/docs/prompt_engineering_pentagi.md` (+14 -0) </details> ### 📄 Description ## Summary - add a pentesting prompt methodology section to the README for prompt authors - expand the prompt engineering guide with a pentester-specific methodology checklist and reference material - point contributors to the existing `examples/prompts/base_web_pentest.md` starter prompt ## Problem Issue #79 asks for better guidance on how AI prompts should approach pentesting. PentAGI already includes prompt templates and a sample web pentest prompt, but the documentation does not explain how to translate pentesting methodology into reusable agent guidance. ## Solution - add a new README section under Development that describes a phase-based prompt methodology for offensive security work - extend `backend/docs/prompt_engineering_pentagi.md` with guidance for authorization boundaries, coverage-first mapping, attack-surface prioritization, low-risk validation, evidence capture, iterative memory use, and report-ready summaries - reference public methodology sources such as HackTricks and Pentest Book as inspiration without copying large external checklists into PentAGI's prompt docs ## User Impact Prompt authors now have a clearer path for turning pentest methodology into PentAGI prompts. This should make new prompt iterations easier to structure, easier to review, and easier to adapt to different engagement scopes. ## Test Plan - confirm the new README section is linked from the table of contents - verify the documentation references existing PentAGI prompt assets and external methodology sources accurately - run `git diff --check` Closes #79 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-06 22:10:01 -04:00
yindo closed this issue 2026-06-06 22:10:01 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#280
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?