[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AR2DGM4WF3GABTGPWP3FDY":3,"skill-same:01M7AR2DGM4WF3GABTGPWP3FDY":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AR2DGM4WF3GABTGPWP3FDY","pentest-red-team-ai-and-reporting",null,"Use when running the adversary-simulation and communication side of an authorized engagement: social engineering and physical testing (within an agreed scope and rules of engagement), red teaming vs purple teaming, post-exploitation reasoning (goals, not tooling), testing AI\u002FLLM systems (OWASP LLM Top 10, prompt injection, the model and its surrounding system) and using AI in offensive work, and reporting — the report as the product, writing a finding that is actually usable (evidence, reproduction, business risk, CVSS), and what happens after the report (retest, remediation support). Authorized, defensive-context work only.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpenetration-testing\u002Fskills\u002Fpentest-red-team-ai-and-reporting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pentest-red-team-ai-and-reporting\ndescription: \"Use when running the adversary-simulation and communication side of an authorized engagement: social engineering and physical testing (within an agreed scope and rules of engagement), red teaming vs purple teaming, post-exploitation reasoning (goals, not tooling), testing AI\u002FLLM systems (OWASP LLM Top 10, prompt injection, the model and its surrounding system) and using AI in offensive work, and reporting — the report as the product, writing a finding that is actually usable (evidence, reproduction, business risk, CVSS), and what happens after the report (retest, remediation support). Authorized, defensive-context work only.\"\n---\n\n# Penetration Testing: Social Engineering, Red\u002FPurple Teaming, Post-Exploitation, AI Systems, and Reporting\n\n> **Part 3 of 4** of the *Penetration Testing and Offensive Security* reference (plugin `penetration-testing`), covering §10–§13. Sibling skills: `pentest-authorization-scoping-and-methodology` (§0–§3), `pentest-technical-domains` (§4–§9), `pentest-disclosure-career-and-reference` (§14–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `pentest-disclosure-career-and-reference` for the currency snapshot and what goes stale first.\n\n> **⚠️ THE PREREQUISITE FOR EVERYTHING BELOW.** The entire difference between this\n> profession and a felony is **documented, informed authorization from someone with the\n> authority to grant it, for a defined scope, in a defined window.** Not implied consent.\n> Not a verbal go-ahead. Not \"the client seemed fine with it.\" Not a bug bounty scope you\n> read quickly. **§1 → `pentest-authorization-scoping-and-methodology` is the section that matters most, and it is first for that reason.**\n>\n> This document is written for people doing authorized work — in-house security teams,\n> consultancies, bug bounty participants operating inside a published scope, and the\n> people who hire and manage them. **It is a methodology, process, and professional\n> practice reference.** It deliberately does not contain exploitation recipes, working\n> exploit code, or techniques for evading specific defensive products; those live in\n> engagement-specific research, and the value of a reference like this is in the parts\n> practitioners actually get wrong — scoping, method, evidence, and communication.\n>\n> **This is not legal advice.** §1 → `pentest-authorization-scoping-and-methodology` tells you what to ask your counsel, not what your\n> obligations are in your jurisdiction.\n\n> **How to read this.** Three markers:\n> - **[DURABLE]** — professional practice, methodology, or a lesson the field has settled.\n> - **[VERSIONED]** — regulation, tooling, market state. Verify.\n> - **[CONTESTED]** — practitioners genuinely disagree.\n>\n> **The three framings that organize everything below:**\n> 1. **The report is the product.** The client is not buying access to their systems —\n>    they already have that. **They are buying a prioritized, reproducible, actionable\n>    understanding of their risk.** A brilliant compromise written up badly is a failed\n>    engagement (§13).\n> 2. **Your job is to model a threat, not to win.** \"I got domain admin\" is not the goal;\n>    **\"here is how an attacker with these capabilities would reach these assets, here is\n>    what detected them and what didn't, and here is what to fix first\"** is.\n> 3. **You are operating in someone's production environment and you can break it.**\n>    Professional restraint — knowing what *not* to run — is a larger part of competence\n>    than the ability to run anything.\n\n---\n\n## §10. Social Engineering and Physical\n\n**[DURABLE] The human layer is consistently the most effective initial access vector**, and\nconsistently the most sensitive to test.\n\n**Techniques**: phishing (and its voice and SMS variants), pretexting, **MFA fatigue and\nconsent phishing**, and physical entry — tailgating, badge cloning, and testing what\nhappens when someone walks in wearing a hi-vis vest.\n\n**⚠️ The ethical and legal handling is different in kind here**, and it is where\nengagements most often cause real harm:\n- **Requires specific, explicit written authorization** naming the techniques.\n- **Physical assessments require the authorization letter on your person**, plus a named\n  contact reachable at any hour who can vouch for you. **Assume you will be detained** and\n  plan for it; also assume law enforcement may be called, which is a serious situation\n  regardless of your paperwork.\n- **Never impersonate law enforcement or government officials.**\n- **Report on the process, not the person.** \"Three of forty staff entered credentials\" is\n  a finding. Naming and shaming individuals is unprofessional, destroys future\n  cooperation, and can be a serious HR and legal matter.\n- **⚠️ Avoid pretexts that cause genuine distress** — fake layoffs, fake bonus\n  announcements, fake emergencies involving family. These have caused real harm, and\n  \"the attacker would do it\" is not sufficient justification when *you* are the one doing\n  it to real employees.\n- Consider works councils, union agreements, and employment law — **in several\n  jurisdictions testing employees has consultation requirements.**\n\n---\n\n## §11. Red Teaming, Purple Teaming, Post-Exploitation\n\n### 11.1 Post-exploitation, conceptually\n\n**[DURABLE] The point of post-exploitation is to establish business impact, not to\nmaximize access.** The questions: what does this foothold reach? What credentials or\ntokens are available here? What would an attacker do next, and what does that reach? **And\ncritically — what did the defenders see?**\n\n**Map everything to MITRE ATT&CK.** It is the shared vocabulary that lets a defender take\nyour report and build a detection, and it turns \"we moved laterally\" into a specific\ntechnique ID they can hunt for.\n\n**⚠️ Restraint applies most here.** Persistence mechanisms must be documented and removed;\n**leave-behinds are how testers cause incidents months later.** Keep a written cleanup\ninventory — every account created, tool dropped, configuration changed, and persistence\nestablished — and **verify removal with the client rather than asserting it.**\n\n### 11.2 Red vs. purple\n\n**Red team** tests **detection and response**, not vulnerabilities. It has an objective\n(reach this data, execute this transaction), a long timeline, and a **blue team that\ndoesn't know** — which is the whole point and also the source of its cost.\n\n**Purple team** puts testers and defenders in the same room: run a technique, check whether\nit alerted, tune the detection, run it again. **[CONTESTED but with a strong majority\nview]: for most organizations, purple teaming delivers more defensive improvement per dollar\nthan red teaming**, because red teaming tells you that you failed while purple teaming\nfixes it. The counter-argument is real: **only an unannounced exercise tests the actual\nhuman response under genuine uncertainty**, and organizations that only purple team never\nlearn whether their process works when nobody is expecting it.\n\n**[DURABLE] The maturity ladder is real: do not buy a red team engagement if you have not\ndone the basic testing.** An organization that hasn't patched its perimeter and has a flat\nnetwork doesn't need an adversary simulation to know it will fail. **Red teaming is\nappropriate when you have a functioning security program and want to test it** — buying one\nearlier is paying premium rates for findings a vulnerability assessment would have given\nyou.\n\n---\n\n## §12. AI Systems\n\n**[DURABLE] Two distinct things share a name, and conflating them causes confusion:\n*testing AI systems* and *using AI to test*.**\n\n### 12.1 Testing AI systems\n\n**[VERSIONED] A genuinely new attack surface with new vulnerability classes** that don't\nmap cleanly onto existing methodology. Scoping guidance now explicitly holds that **once AI\nfeatures are part of the application boundary, the test has to ask different questions**\nabout providers, self-hosting, output handling, keys, logging, and worst-case impact.\n\n**What you're testing for**: **prompt injection** (direct and indirect — and note that\nthis is **not solved**, so any system giving a model tools plus untrusted input has real\nexposure), **insecure output handling** (model output reaching an interpreter, a browser,\nor a shell), **excessive agency** (what can the agent's tools actually do, and what happens\nwhen it's manipulated into doing it), **data leakage** through retrieval systems and\ncontext, **training data and model supply chain**, and **denial-of-wallet**. **OWASP's LLM\nand Agentic Applications material** is the reference framework.\n\n### 12.2 AI in offensive work\n\n**[VERSIONED] This moved from novelty to material capability faster than almost anything\nelse in the field, and the honest picture cuts both ways.**\n\n**What the evidence shows:**\n- **Adoption is near-universal.** Bugcrowd's 2026 research reports **82% of hackers already\n  use AI in their workflows**, mainly for automation, code analysis, and getting unstuck.\n- **The capability is real.** **XBOW's autonomous agent took #1 on HackerOne in June 2025**\n  and later published 1,060+ valid submissions. **ARTEMIS (December 2025) reportedly beat\n  9 of 10 human pentesters on a live 8,000-host enterprise network at $18\u002Fhour.** A\n  February 2026 benchmark of an LLM agent on a realistic five-host Active Directory\n  engagement **compromised four of five hosts for $28.50 in API fees**, running multiple\n  exploitation paths concurrently.\n- **Adversaries use it too.** Google's threat intelligence confirms attackers integrating\n  AI for reconnaissance, social engineering, and exploit work.\n- **The productivity gain is measurable and mundane**: reported ~**35% reduction in\n  time-to-report**, which makes sense given how much of a report is templated (§13).\n\n**What the evidence also shows:**\n- **The gap is judgment, not execution.** Synack's CTO frames it well: AI performs broad\n  attack-surface reconnaissance well, but **\"where AI often falls short is in contextual\n  understanding and creativity. Humans infer business logic that AI will sometimes miss\"** —\n  which is precisely §5.1 → `pentest-technical-domains`'s highest-value finding category.\n- **Practitioners can't drive it well yet.** A HackerOne survey found **54% of respondents\n  lacked the skills to effectively prompt, evaluate, and course-correct AI tools** during\n  offensive work.\n- **⚠️ It introduces new operational risk.** Handing an autonomous agent offensive tooling\n  against live systems raises real safety and scope questions — **an agent that adapts is\n  an agent that can wander outside where you meant it to go.** In an engagement governed by\n  §1 → `pentest-authorization-scoping-and-methodology`'s rules of engagement, that is not a minor concern; it is a potential authorization\n  violation with your name on it. Platforms addressing this use graduated trust levels and\n  hard-blocked destructive commands.\n- **The vulnerability-report ecosystem is straining.** AI-generated reports at volume are a\n  live problem for maintainers and triage teams.\n\n**⚠️ The marketing substantially outruns the evidence**, and this is a domain where vendor\nmaterial dominates the search results. **\"Manual pentesting will be a boutique service by\n2027\" is a vendor claim, not a finding.** The defensible position: **treat AI agents as\naugmented operators, not replacements**, keep a human accountable for scope and for the\nreport, and note that the parts of the job with the highest client value — scoping,\nbusiness-logic reasoning, impact judgment, and communication (§13) — are exactly the parts\nthe tooling is weakest at.\n\n---\n\n## §13. Reporting\n\n**[DURABLE] This is the product. Everything before it is raw material.**\n\n### 13.1 The structure\n\n```\nEXECUTIVE SUMMARY      1–2 pages, no jargon. What was tested, what the risk is,\n                       what to do first. ⚠️ Assume this is ALL an executive reads\nSCOPE & METHODOLOGY    exactly what was and wasn't tested, when, by what method,\n                       and the LIMITATIONS (time-boxed? staging? credentialed?)\nFINDINGS SUMMARY       table: ID, title, severity, affected asset, status\nDETAILED FINDINGS      one per finding — the core of the document (§13.2)\nSTRATEGIC OBSERVATIONS the patterns behind the findings. Often the most valuable page\nAPPENDICES             tooling, source IPs, full output, timeline\n```\n\n### 13.2 A finding that is actually usable\n\nEvery finding needs: **a title that names the issue**, **severity with the reasoning shown**\n(CVSS if you use it — **and state the vector string**, because a bare number is\nunfalsifiable), **affected assets enumerated**, **a plain-language description of what it\nis**, **business impact in the client's terms** (\"an unauthenticated attacker can read any\ncustomer's records\" — not \"IDOR in the user endpoint\"), **reproduction steps a competent\nengineer can follow without you**, **evidence** (redacted screenshots, requests\u002Fresponses),\n**specific remediation** — not \"validate input\" but what to change, where, and to what —\nplus references (CWE, vendor docs), and **retest status**.\n\n> **⚠️ GOTCHA — the reporting failures that waste the engagement:**\n> - **Severity inflation.** Rating everything high destroys your credibility and the\n>   client's ability to prioritize. **If everything is critical, nothing is.**\n> - **CVSS base score used as the priority.** Base score ignores your client's environment\n>   entirely. **Use environmental\u002Ftemporal metrics, or say plainly that the score is a\n>   starting point.** Consider **EPSS** for likelihood-of-exploitation context.\n> - **Scanner output pasted in as findings.** Unverified findings are the fastest way to be\n>   dismissed. **Verify everything you report, or label it explicitly as unverified.**\n> - **No reproduction steps**, so the fix can't be validated.\n> - **Generic remediation** copied from a template.\n> - **Burying the important finding** among forty informational ones.\n> - **Missing the pattern.** Fifteen instances of missing access control is one systemic\n>   finding about how the team builds authorization — **say that**, because fixing fifteen\n>   endpoints doesn't fix the sixteenth they ship next month.\n> - **No negative findings.** \"We tested X and found it well-implemented\" is genuinely\n>   valuable and almost never written.\n\n**[DURABLE] Write the executive summary for someone who will make a budget decision from it\nand read nothing else.** That is not a compromise; that is the job.\n\n### 13.3 After the report\n\n**Debrief both audiences** — technical walkthrough for engineers, risk framing for\nleadership. **Support remediation** (the questions afterwards are where a lot of real value\ntransfers). **Retest and issue a delta.** And **handle the artifacts**: destroy engagement\ndata per the agreed schedule, confirm in writing, and remove every persistence mechanism\nand account from §11.1's inventory.\n","# Penetration Testing: Social Engineering, Red\u002FPurple Teaming, Post-Exploitation, AI Systems, and Reporting\n\n> **Part 3 of 4** of the *Penetration Testing and Offensive Security* reference (plugin `penetration-testing`), covering §10–§13. Sibling skills: `pentest-authorization-scoping-and-methodology` (§0–§3), `pentest-technical-domains` (§4–§9), `pentest-disclosure-career-and-reference` (§14–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `pentest-disclosure-career-and-reference` for the currency snapshot and what goes stale first.\n\n> **⚠️ THE PREREQUISITE FOR EVERYTHING BELOW.** The entire difference between this\n> profession and a felony is **documented, informed authorization from someone with the\n> authority to grant it, for a defined scope, in a defined window.** Not implied consent.\n> Not a verbal go-ahead. Not \"the client seemed fine with it.\" Not a bug bounty scope you\n> read quickly. **§1 → `pentest-authorization-scoping-and-methodology` is the section that matters most, and it is first for that reason.**\n>\n> This document is written for people doing authorized work — in-house security teams,\n> consultancies, bug bounty participants operating inside a published scope, and the\n> people who hire and manage them. **It is a methodology, process, and professional\n> practice reference.** It deliberately does not contain exploitation recipes, working\n> exploit code, or techniques for evading specific defensive products; those live in\n> engagement-specific research, and the value of a reference like this is in the parts\n> practitioners actually get wrong — scoping, method, evidence, and communication.\n>\n> **This is not legal advice.** §1 → `pentest-authorization-scoping-and-methodology` tells you what to ask your counsel, not what your\n> obligations are in your jurisdiction.\n\n> **How to read this.** Three markers:\n> - **[DURABLE]** — professional practice, methodology, or a lesson the field has settled.\n> - **[VERSIONED]** — regulation, tooling, market state. Verify.\n> - **[CONTESTED]** — practitioners genuinely disagree.\n>\n> **The three framings that organize everything below:**\n> 1. **The report is the product.** The client is not buying access to their systems —\n>    they already have that. **They are buying a prioritized, reproducible, actionable\n>    understanding of their risk.** A brilliant compromise written up badly is a failed\n>    engagement (§13).\n> 2. **Your job is to model a threat, not to win.** \"I got domain admin\" is not the goal;\n>    **\"here is how an attacker with these capabilities would reach these assets, here is\n>    what detected them and what didn't, and here is what to fix first\"** is.\n> 3. **You are operating in someone's production environment and you can break it.**\n>    Professional restraint — knowing what *not* to run — is a larger part of competence\n>    than the ability to run anything.\n\n---\n\n## §10. Social Engineering and Physical\n\n**[DURABLE] The human layer is consistently the most effective initial access vector**, and\nconsistently the most sensitive to test.\n\n**Techniques**: phishing (and its voice and SMS variants), pretexting, **MFA fatigue and\nconsent phishing**, and physical entry — tailgating, badge cloning, and testing what\nhappens when someone walks in wearing a hi-vis vest.\n\n**⚠️ The ethical and legal handling is different in kind here**, and it is where\nengagements most often cause real harm:\n- **Requires specific, explicit written authorization** naming the techniques.\n- **Physical assessments require the authorization letter on your person**, plus a named\n  contact reachable at any hour who can vouch for you. **Assume you will be detained** and\n  plan for it; also assume law enforcement may be called, which is a serious situation\n  regardless of your paperwork.\n- **Never impersonate law enforcement or government officials.**\n- **Report on the process, not the person.** \"Three of forty staff entered credentials\" is\n  a finding. Naming and shaming individuals is unprofessional, destroys future\n  cooperation, and can be a serious HR and legal matter.\n- **⚠️ Avoid pretexts that cause genuine distress** — fake layoffs, fake bonus\n  announcements, fake emergencies involving family. These have caused real harm, and\n  \"the attacker would do it\" is not sufficient justification when *you* are the one doing\n  it to real employees.\n- Consider works councils, union agreements, and employment law — **in several\n  jurisdictions testing employees has consultation requirements.**\n\n---\n\n## §11. Red Teaming, Purple Teaming, Post-Exploitation\n\n### 11.1 Post-exploitation, conceptually\n\n**[DURABLE] The point of post-exploitation is to establish business impact, not to\nmaximize access.** The questions: what does this foothold reach? What credentials or\ntokens are available here? What would an attacker do next, and what does that reach? **And\ncritically — what did the defenders see?**\n\n**Map everything to MITRE ATT&CK.** It is the shared vocabulary that lets a defender take\nyour report and build a detection, and it turns \"we moved laterally\" into a specific\ntechnique ID they can hunt for.\n\n**⚠️ Restraint applies most here.** Persistence mechanisms must be documented and removed;\n**leave-behinds are how testers cause incidents months later.** Keep a written cleanup\ninventory — every account created, tool dropped, configuration changed, and persistence\nestablished — and **verify removal with the client rather than asserting it.**\n\n### 11.2 Red vs. purple\n\n**Red team** tests **detection and response**, not vulnerabilities. It has an objective\n(reach this data, execute this transaction), a long timeline, and a **blue team that\ndoesn't know** — which is the whole point and also the source of its cost.\n\n**Purple team** puts testers and defenders in the same room: run a technique, check whether\nit alerted, tune the detection, run it again. **[CONTESTED but with a strong majority\nview]: for most organizations, purple teaming delivers more defensive improvement per dollar\nthan red teaming**, because red teaming tells you that you failed while purple teaming\nfixes it. The counter-argument is real: **only an unannounced exercise tests the actual\nhuman response under genuine uncertainty**, and organizations that only purple team never\nlearn whether their process works when nobody is expecting it.\n\n**[DURABLE] The maturity ladder is real: do not buy a red team engagement if you have not\ndone the basic testing.** An organization that hasn't patched its perimeter and has a flat\nnetwork doesn't need an adversary simulation to know it will fail. **Red teaming is\nappropriate when you have a functioning security program and want to test it** — buying one\nearlier is paying premium rates for findings a vulnerability assessment would have given\nyou.\n\n---\n\n## §12. AI Systems\n\n**[DURABLE] Two distinct things share a name, and conflating them causes confusion:\n*testing AI systems* and *using AI to test*.**\n\n### 12.1 Testing AI systems\n\n**[VERSIONED] A genuinely new attack surface with new vulnerability classes** that don't\nmap cleanly onto existing methodology. Scoping guidance now explicitly holds that **once AI\nfeatures are part of the application boundary, the test has to ask different questions**\nabout providers, self-hosting, output handling, keys, logging, and worst-case impact.\n\n**What you're testing for**: **prompt injection** (direct and indirect — and note that\nthis is **not solved**, so any system giving a model tools plus untrusted input has real\nexposure), **insecure output handling** (model output reaching an interpreter, a browser,\nor a shell), **excessive agency** (what can the agent's tools actually do, and what happens\nwhen it's manipulated into doing it), **data leakage** through retrieval systems and\ncontext, **training data and model supply chain**, and **denial-of-wallet**. **OWASP's LLM\nand Agentic Applications material** is the reference framework.\n\n### 12.2 AI in offensive work\n\n**[VERSIONED] This moved from novelty to material capability faster than almost anything\nelse in the field, and the honest picture cuts both ways.**\n\n**What the evidence shows:**\n- **Adoption is near-universal.** Bugcrowd's 2026 research reports **82% of hackers already\n  use AI in their workflows**, mainly for automation, code analysis, and getting unstuck.\n- **The capability is real.** **XBOW's autonomous agent took #1 on HackerOne in June 2025**\n  and later published 1,060+ valid submissions. **ARTEMIS (December 2025) reportedly beat\n  9 of 10 human pentesters on a live 8,000-host enterprise network at $18\u002Fhour.** A\n  February 2026 benchmark of an LLM agent on a realistic five-host Active Directory\n  engagement **compromised four of five hosts for $28.50 in API fees**, running multiple\n  exploitation paths concurrently.\n- **Adversaries use it too.** Google's threat intelligence confirms attackers integrating\n  AI for reconnaissance, social engineering, and exploit work.\n- **The productivity gain is measurable and mundane**: reported ~**35% reduction in\n  time-to-report**, which makes sense given how much of a report is templated (§13).\n\n**What the evidence also shows:**\n- **The gap is judgment, not execution.** Synack's CTO frames it well: AI performs broad\n  attack-surface reconnaissance well, but **\"where AI often falls short is in contextual\n  understanding and creativity. Humans infer business logic that AI will sometimes miss\"** —\n  which is precisely §5.1 → `pentest-technical-domains`'s highest-value finding category.\n- **Practitioners can't drive it well yet.** A HackerOne survey found **54% of respondents\n  lacked the skills to effectively prompt, evaluate, and course-correct AI tools** during\n  offensive work.\n- **⚠️ It introduces new operational risk.** Handing an autonomous agent offensive tooling\n  against live systems raises real safety and scope questions — **an agent that adapts is\n  an agent that can wander outside where you meant it to go.** In an engagement governed by\n  §1 → `pentest-authorization-scoping-and-methodology`'s rules of engagement, that is not a minor concern; it is a potential authorization\n  violation with your name on it. Platforms addressing this use graduated trust levels and\n  hard-blocked destructive commands.\n- **The vulnerability-report ecosystem is straining.** AI-generated reports at volume are a\n  live problem for maintainers and triage teams.\n\n**⚠️ The marketing substantially outruns the evidence**, and this is a domain where vendor\nmaterial dominates the search results. **\"Manual pentesting will be a boutique service by\n2027\" is a vendor claim, not a finding.** The defensible position: **treat AI agents as\naugmented operators, not replacements**, keep a human accountable for scope and for the\nreport, and note that the parts of the job with the highest client value — scoping,\nbusiness-logic reasoning, impact judgment, and communication (§13) — are exactly the parts\nthe tooling is weakest at.\n\n---\n\n## §13. Reporting\n\n**[DURABLE] This is the product. Everything before it is raw material.**\n\n### 13.1 The structure\n\n```\nEXECUTIVE SUMMARY      1–2 pages, no jargon. What was tested, what the risk is,\n                       what to do first. ⚠️ Assume this is ALL an executive reads\nSCOPE & METHODOLOGY    exactly what was and wasn't tested, when, by what method,\n                       and the LIMITATIONS (time-boxed? staging? credentialed?)\nFINDINGS SUMMARY       table: ID, title, severity, affected asset, status\nDETAILED FINDINGS      one per finding — the core of the document (§13.2)\nSTRATEGIC OBSERVATIONS the patterns behind the findings. Often the most valuable page\nAPPENDICES             tooling, source IPs, full output, timeline\n```\n\n### 13.2 A finding that is actually usable\n\nEvery finding needs: **a title that names the issue**, **severity with the reasoning shown**\n(CVSS if you use it — **and state the vector string**, because a bare number is\nunfalsifiable), **affected assets enumerated**, **a plain-language description of what it\nis**, **business impact in the client's terms** (\"an unauthenticated attacker can read any\ncustomer's records\" — not \"IDOR in the user endpoint\"), **reproduction steps a competent\nengineer can follow without you**, **evidence** (redacted screenshots, requests\u002Fresponses),\n**specific remediation** — not \"validate input\" but what to change, where, and to what —\nplus references (CWE, vendor docs), and **retest status**.\n\n> **⚠️ GOTCHA — the reporting failures that waste the engagement:**\n> - **Severity inflation.** Rating everything high destroys your credibility and the\n>   client's ability to prioritize. **If everything is critical, nothing is.**\n> - **CVSS base score used as the priority.** Base score ignores your client's environment\n>   entirely. **Use environmental\u002Ftemporal metrics, or say plainly that the score is a\n>   starting point.** Consider **EPSS** for likelihood-of-exploitation context.\n> - **Scanner output pasted in as findings.** Unverified findings are the fastest way to be\n>   dismissed. **Verify everything you report, or label it explicitly as unverified.**\n> - **No reproduction steps**, so the fix can't be validated.\n> - **Generic remediation** copied from a template.\n> - **Burying the important finding** among forty informational ones.\n> - **Missing the pattern.** Fifteen instances of missing access control is one systemic\n>   finding about how the team builds authorization — **say that**, because fixing fifteen\n>   endpoints doesn't fix the sixteenth they ship next month.\n> - **No negative findings.** \"We tested X and found it well-implemented\" is genuinely\n>   valuable and almost never written.\n\n**[DURABLE] Write the executive summary for someone who will make a budget decision from it\nand read nothing else.** That is not a compromise; that is the job.\n\n### 13.3 After the report\n\n**Debrief both audiences** — technical walkthrough for engineers, risk framing for\nleadership. **Support remediation** (the questions afterwards are where a lot of real value\ntransfers). **Retest and issue a delta.** And **handle the artifacts**: destroy engagement\ndata per the agreed schedule, confirm in writing, and remove every persistence mechanism\nand account from §11.1's inventory.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpenetration-testing\u002Fskills\u002Fpentest-red-team-ai-and-reporting",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill pentest-red-team-ai-and-reporting",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill pentest-red-team-ai-and-reporting",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill pentest-red-team-ai-and-reporting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fpenetration-testing\u002Fskills\u002Fpentest-red-team-ai-and-reporting\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]