Add measured ProjectDiscovery reconnaissance to web-security#105
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
initial-reconskill for domain, wildcard, ASN, IP-list, and CIDR entry pointsscripts/pd-toolentry point, including explicit protection from PythonhttpxPATH collisionsApproach
The web-security agent keeps its existing focused OODA loop. Broad scopes now load progressive recon context on demand rather than expanding the base prompt. The skill uses the ProjectDiscovery binaries already provisioned by the capability and hands ranked responsive assets back to normal web-security testing.
The resolver checks
$PDTM_BIN_DIR, the standard PDTM install directory, the Go binary directory, and finally PATH.httpxfrom PATH is accepted only when its version output identifies the ProjectDiscovery implementation.The coverage ledger records observed completion rather than planned work, so interrupted or deferred phases remain visible without being counted as comprehensive coverage.
Validation
303 passedacross the full web-security test suite16 passedin the new focused recon testsjust validatecompleted with no capability failures; existing optional local checks remain warningsscripts/pd-toolFollow-up
A future change can add a dedicated large-scope recon agent or worker pipeline with explicit phase budgets and child-run cost accounting. This change intentionally keeps orchestration out of scope and adds only the context and deterministic helpers needed by the existing web-security agent.