What the reviewer found
A bug-bounty methodology playbook: the SSRF-to-cloud-metadata table, the Firebase write-test curl, the tj-actions memdump description, and the grep patterns are all techniques for testing a target the reader is authorized to test, not code the file executes on its own. Standard dual-use pentest documentation, gated on the reader having permission to test the target.
dual-use— a security tool that can be misusednetwork— calls the vendor’s API
What was read
The file as it ships in 26zl/cybersec-toolkit:
.claude/skills/bug-bounty/SKILL.md
What the static scan said
The scan flagged 7things. The reviewer kept 0 and dismissed 7 as false.
P1Instruction-override phrasing — false positiveP2Hidden instructions — false positiveE1Sends data to an external URL — false positiveE2Harvests environment variables — false positiveSSRF1Cloud metadata endpoint — false positiveNETMakes network calls — false positiveSHRuns shell commands — false positive
How this review was made
Sonnet 5 read the files above on 7 September 2026 and answered three questions: is it dangerous to whoever installs it, is each scanner finding real, and what should the installer know. The verdict is bound to the file's hash; when the file changes, it is scanned afresh and reviewed again. A script that changes while the definition does not is not re-reviewed — that is a known gap. How the scan and the review work.