Hunt LLM/AI — bug-hunting playbook for LLM and agentic AI vulnerabilities (prompt injection, exfiltration, ASCII smuggling)

Prerequisites: explicit authorization to test the target systems (your own systems, bug-bounty scope, or a penetration-testing engagement) plus OOB infrastructure for proof (e.g. Burp Collaborator, interactsh, or a webhook listener) — ⚠️ AUTHORIZED USE ONLY Install "Hunt LLM/AI — bug-hunting playbook for LLM and agentic AI vulnerabilities" for me. It gives my agent @elementalsouls' rigorous playbook for hunting bugs in LLM/AI features: apply the False-Positive Gate first (run-twice verbatim reproducibility, anchor to a known secret, verifiable cross-tenant artifacts, OOB-confirmed exfil), test direct and indirect prompt injection, markdown-image zero-click and tool-use exfiltration with OOB proof, ASCII/Unicode smuggling, system-prompt and config leakage, IDOR-via-AI and memory/RAG poisoning, backend fingerprinting, AI code-review sabotage, and triage against the ASI01–ASI10 agentic security table. Dual-use tooling — authorized testing only. MIT-licensed. Repository: https://github.com/elementalsouls/claude-bughunter/blob/main/skills/hunt-llm-ai/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "hunt-llm-ai". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. set up my OOB listener and confirm I have explicit authorization for every target; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.