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 #276] [MERGED] docs: add scope-of-work pentest template #289

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

📋 Pull Request Information

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

Base: feature/next-release ← Head: codex/issue-71-scope-of-work-template

📝 Commits (2)

  • 5bc534c docs: add scope-of-work pentest template
  • de6f527 Apply suggestions from code review

📊 Changes

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

View changed files

📝 backend/docs/prompt_engineering_pentagi.md (+1 -0)
➕ examples/prompts/scope_of_work_pentest.md (+87 -0)

📄 Description

Summary

  • add a reusable scope-of-work prompt template for authorized pentest flows
  • cover allowlists, denied targets, stop conditions, evidence expectations, mass scans, generated scripts, and custom exploit checks
  • link the template from the PentAGI prompt engineering guide

Validation

  • git diff --check
  • verified the prompt engineering guide link target exists

Refs #71

🔄 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/276 **Author:** [@mason5052](https://github.com/mason5052) **Created:** 4/22/2026 **Status:** ✅ Merged **Merged:** 4/28/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `feature/next-release` ← **Head:** `codex/issue-71-scope-of-work-template` --- ### 📝 Commits (2) - [`5bc534c`](https://github.com/vxcontrol/pentagi/commit/5bc534c5902c27f2e2885723a47cf569f9172d26) docs: add scope-of-work pentest template - [`de6f527`](https://github.com/vxcontrol/pentagi/commit/de6f527e6f4f4e87a43f535068c44c94cbdfac11) Apply suggestions from code review ### 📊 Changes **2 files changed** (+88 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `backend/docs/prompt_engineering_pentagi.md` (+1 -0) ➕ `examples/prompts/scope_of_work_pentest.md` (+87 -0) </details> ### 📄 Description ## Summary - add a reusable scope-of-work prompt template for authorized pentest flows - cover allowlists, denied targets, stop conditions, evidence expectations, mass scans, generated scripts, and custom exploit checks - link the template from the PentAGI prompt engineering guide ## Validation - `git diff --check` - verified the prompt engineering guide link target exists Refs #71 --- <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:04 -04:00
yindo closed this issue 2026-06-06 22:10:04 -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#289
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?