[PR #278] [MERGED] docs: add OSINT integration scenarios #292

New Issue

2026-06-06T22:10:04-04:00

yindo commented

2026-06-06 22:10:04 -04:00

📋 Pull Request Information

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

Base: feature/next-release ← Head: codex/issue-68-osint-scenarios

📝 Commits (4)

c7e9084 docs: add OSINT integration scenarios
54b958d docs: clarify OSINT scenario payloads
0f331e3 docs: clarify OSINT provider identifiers
44e6c97 docs: distinguish OSINT provider ids

📊 Changes

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

View changed files

📝 backend/docs/config.md (+2 -0)
➕ examples/guides/osint-integration-scenarios.md (+158 -0)

📄 Description

Summary

add provider-neutral OSINT integration scenarios for ransomware.live and Flare
answer when agents should query these providers, which data categories are useful, and what outputs should feed reports
document guardrails so OSINT enrichment does not expand pentest scope or encourage credential misuse
link the guide from the external functions configuration docs

Validation

git diff --check
verified the config docs link target exists
checked current ransomware.live and Flare API docs while drafting endpoint categories and scenarios

Refs #68

_{🔄 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/278 **Author:** [@mason5052](https://github.com/mason5052) **Created:** 4/22/2026 **Status:** ✅ Merged **Merged:** 4/30/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `feature/next-release` ← **Head:** `codex/issue-68-osint-scenarios` --- ### 📝 Commits (4) - [`c7e9084`](https://github.com/vxcontrol/pentagi/commit/c7e90849a73d0a0863179bc1efd6c10d1198c4d9) docs: add OSINT integration scenarios - [`54b958d`](https://github.com/vxcontrol/pentagi/commit/54b958d5db0a1f909f51b4db11a1803dbed2e36c) docs: clarify OSINT scenario payloads - [`0f331e3`](https://github.com/vxcontrol/pentagi/commit/0f331e3e95e3b06100dbef0aee4067826af7f119) docs: clarify OSINT provider identifiers - [`44e6c97`](https://github.com/vxcontrol/pentagi/commit/44e6c97e5e828e5bb2f7ec67ebd55b73f8390e6e) docs: distinguish OSINT provider ids ### 📊 Changes **2 files changed** (+160 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `backend/docs/config.md` (+2 -0) ➕ `examples/guides/osint-integration-scenarios.md` (+158 -0) </details> ### 📄 Description ## Summary - add provider-neutral OSINT integration scenarios for ransomware.live and Flare - answer when agents should query these providers, which data categories are useful, and what outputs should feed reports - document guardrails so OSINT enrichment does not expand pentest scope or encourage credential misuse - link the guide from the external functions configuration docs ## Validation - `git diff --check` - verified the config docs link target exists - checked current ransomware.live and Flare API docs while drafting endpoint categories and scenarios Refs #68 --- <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

yindo referenced this issue

2026-06-06 22:10:07 -04:00

[PR #292] [MERGED] docs: explain assistant flow management for active flows #301

yindo referenced this issue

2026-06-06 22:10:10 -04:00

[PR #306] [MERGED] docs(rfc): propose persistent flow queue and completion webhooks #311

Sign in to join this conversation.