[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EHCSMEBQQCK5SEBZKWYCFM":3,"skill-same:01M7EHCSMEBQQCK5SEBZKWYCFM":49},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7EHCSMEBQQCK5SEBZKWYCFM","bounty-report-formatter",null,"Bug bounty report formatting for HackerOne, Bugcrowd, Immunefi, and GitHub Security Advisories. Load after validate_finding succeeds and the finding needs to be submitted to a bounty program.","a18268941610-crypto\u002FDecepticon-shentou","a18268941610-crypto","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F241464571?v=4","01M7EHA2V2KTCYTX78QJKXCZ8Y","fubai","01M7EHA2VKDD5RCWJJKC0ZA101",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fplugins\u002Fverifier\u002Fbounty-report\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bounty-report-formatter\ndescription: Bug bounty report formatting for HackerOne, Bugcrowd, Immunefi, and GitHub Security Advisories. Load after validate_finding succeeds and the finding needs to be submitted to a bounty program.\nmetadata:\n  subdomain: reporting\n  when_to_use: \"bug bounty report hackerone h1 bugcrowd immunefi github security advisory ghsa submission triage cvss writeup\"\n  upstream_ref: \"HackerOne \u002F Bugcrowd \u002F Immunefi \u002F GitHub Security Advisory submission templates\"\n---\n\n# Bug Bounty Report Formatter\n\nFormat validated findings as platform-ready bug bounty reports that\nsurvive triage. Optimized for acceptance rate, not word count. The\nstandard this targets: 7.00 HackerOne signal — precision over volume.\n\n## Title Convention\n\nFormat: `[Component]: [Vulnerability Class] via [Mechanism]`\n\nGood titles (from real accepted advisories):\n- `zrok: WebDAV drive backend follows symlinks outside DriveRoot, enabling host filesystem read\u002Fwrite`\n- `Parse Server: cloud function validator bypass via prototype chain traversal`\n- `Directus: TUS Upload Authorization Bypass Allows Arbitrary File Overwrite`\n- `lodash: Code Injection via _.template imports key names`\n- `AVideo: Unauthenticated SSRF via HTTP redirect bypass in LiveLinks proxy`\n- `OpenFGA: Unauthenticated playground endpoint discloses preshared API key`\n\nRules:\n- Component name first (the project\u002Fpackage name)\n- Vulnerability class in plain English (not CWE numbers in the title)\n- Mechanism must be specific (not \"via user input\" — say \"via prototype chain traversal\")\n- No adjectives like \"critical\" or \"severe\" in the title\n- Under 120 characters\n\n## Report Template\n\nWrite to `workspace\u002Ffindings\u002FBOUNTY-{finding_id}.md`:\n\n```markdown\n# {Title}\n\n## Summary\n\n{One paragraph. State what the bug is, where it lives (file:line or endpoint),\nand what impact it has. Three sentences maximum.}\n\n## Severity\n\n**CVSS 3.1**: {full vector string} ({score} {severity_label})\n\n| Metric | Value | Justification |\n|--------|-------|---------------|\n| AV | Network | Exploitable over HTTP |\n| AC | Low | No special conditions |\n| PR | None | No authentication required |\n| UI | None | No user interaction |\n| S | Unchanged | Impact limited to vulnerable component |\n| C | High | Full read access to filesystem |\n| I | None | No write capability demonstrated |\n| A | None | No availability impact |\n\n## Affected Version\n\n- Package: {name}\n- Version: {exact version or range}\n- Commit: {commit hash if applicable}\n\n## Steps to Reproduce\n\n1. {Exact setup step — e.g., \"Clone the repository: `git clone ...`\"}\n2. {Exact action — e.g., \"Start the server: `npm start`\"}\n3. {Exact exploit — e.g., \"Send the following request:\"}\n\n## Proof of Concept\n\n\\```bash\n{Exact command that demonstrates the vulnerability}\n\\```\n\n**Expected response (vulnerable):**\n\\```\n{Exact output showing exploitation}\n\\```\n\n**Baseline response (not vulnerable):**\n\\```\n{Output from the same request without the payload}\n\\```\n\n## Impact\n\n{What an attacker can actually do with this bug. Only state impacts you\ndemonstrated in the PoC. Do NOT extrapolate to theoretical scenarios.}\n\n## Remediation\n\n{Specific code fix. Show the diff or the corrected code.}\n\n\\```diff\n- const user = db.query(`SELECT * FROM users WHERE id=${req.params.id}`)\n+ const user = db.query(`SELECT * FROM users WHERE id=$1`, [req.params.id])\n\\```\n```\n\n## Quality Checklist\n\nBefore writing the report, verify each item:\n\n- [ ] Title follows `Component: VulnClass via Mechanism` format\n- [ ] Summary is ≤3 sentences\n- [ ] CVSS vector string is complete (not just a number)\n- [ ] Every CVSS metric has a justification (not default values)\n- [ ] Steps to reproduce are exact commands, not descriptions\n- [ ] PoC is a single copy-pasteable command\n- [ ] Baseline\u002Fnegative response is included (proves the PoC is meaningful)\n- [ ] Impact describes only demonstrated effects\n- [ ] Remediation is a specific code fix, not generic advice\n- [ ] Affected version is exact (not \"all versions\" unless verified)\n- [ ] Total report is under 500 words (excluding code blocks)\n- [ ] No filler phrases: \"an attacker could potentially\", \"this might allow\",\n      \"it is recommended to\", \"in certain conditions\"\n- [ ] No severity inflation beyond what the PoC proves\n- [ ] Finding is in scope for the target program\n- [ ] Not a duplicate of an existing finding (`kg_query(kind=\"finding\")`)\n\n## Platform-Specific Notes\n\n### HackerOne\n- Use their severity rating (maps from CVSS)\n- Reference CWE numbers in the weakness field\n- Attach PoC scripts as files if longer than 10 lines\n- Include the CVSS calculator link: `https:\u002F\u002Fwww.first.org\u002Fcvss\u002Fcalculator\u002F3.1#CVSS:3.1\u002F...`\n\n### Bugcrowd\n- Map to their Vulnerability Rating Taxonomy (VRT)\n- P1 = Critical (9.0-10.0), P2 = High (7.0-8.9), P3 = Medium (4.0-6.9), P4 = Low (0.1-3.9)\n\n### GitHub Security Advisories\n- Use the GHSA template: affected package, affected versions, patched versions\n- Include the CWE in the advisory metadata\n- Credit field: your username or team name\n\n### Immunefi\n- Web3\u002FDeFi focus: quantify financial impact when possible\n- Include affected contract addresses if applicable\n- Reference the specific bounty program's scope document\n","# Bug Bounty Report Formatter\n\nFormat validated findings as platform-ready bug bounty reports that\nsurvive triage. Optimized for acceptance rate, not word count. The\nstandard this targets: 7.00 HackerOne signal — precision over volume.\n\n## Title Convention\n\nFormat: `[Component]: [Vulnerability Class] via [Mechanism]`\n\nGood titles (from real accepted advisories):\n- `zrok: WebDAV drive backend follows symlinks outside DriveRoot, enabling host filesystem read\u002Fwrite`\n- `Parse Server: cloud function validator bypass via prototype chain traversal`\n- `Directus: TUS Upload Authorization Bypass Allows Arbitrary File Overwrite`\n- `lodash: Code Injection via _.template imports key names`\n- `AVideo: Unauthenticated SSRF via HTTP redirect bypass in LiveLinks proxy`\n- `OpenFGA: Unauthenticated playground endpoint discloses preshared API key`\n\nRules:\n- Component name first (the project\u002Fpackage name)\n- Vulnerability class in plain English (not CWE numbers in the title)\n- Mechanism must be specific (not \"via user input\" — say \"via prototype chain traversal\")\n- No adjectives like \"critical\" or \"severe\" in the title\n- Under 120 characters\n\n## Report Template\n\nWrite to `workspace\u002Ffindings\u002FBOUNTY-{finding_id}.md`:\n\n```markdown\n# {Title}\n\n## Summary\n\n{One paragraph. State what the bug is, where it lives (file:line or endpoint),\nand what impact it has. Three sentences maximum.}\n\n## Severity\n\n**CVSS 3.1**: {full vector string} ({score} {severity_label})\n\n| Metric | Value | Justification |\n|--------|-------|---------------|\n| AV | Network | Exploitable over HTTP |\n| AC | Low | No special conditions |\n| PR | None | No authentication required |\n| UI | None | No user interaction |\n| S | Unchanged | Impact limited to vulnerable component |\n| C | High | Full read access to filesystem |\n| I | None | No write capability demonstrated |\n| A | None | No availability impact |\n\n## Affected Version\n\n- Package: {name}\n- Version: {exact version or range}\n- Commit: {commit hash if applicable}\n\n## Steps to Reproduce\n\n1. {Exact setup step — e.g., \"Clone the repository: `git clone ...`\"}\n2. {Exact action — e.g., \"Start the server: `npm start`\"}\n3. {Exact exploit — e.g., \"Send the following request:\"}\n\n## Proof of Concept\n\n\\```bash\n{Exact command that demonstrates the vulnerability}\n\\```\n\n**Expected response (vulnerable):**\n\\```\n{Exact output showing exploitation}\n\\```\n\n**Baseline response (not vulnerable):**\n\\```\n{Output from the same request without the payload}\n\\```\n\n## Impact\n\n{What an attacker can actually do with this bug. Only state impacts you\ndemonstrated in the PoC. Do NOT extrapolate to theoretical scenarios.}\n\n## Remediation\n\n{Specific code fix. Show the diff or the corrected code.}\n\n\\```diff\n- const user = db.query(`SELECT * FROM users WHERE id=${req.params.id}`)\n+ const user = db.query(`SELECT * FROM users WHERE id=$1`, [req.params.id])\n\\```\n```\n\n## Quality Checklist\n\nBefore writing the report, verify each item:\n\n- [ ] Title follows `Component: VulnClass via Mechanism` format\n- [ ] Summary is ≤3 sentences\n- [ ] CVSS vector string is complete (not just a number)\n- [ ] Every CVSS metric has a justification (not default values)\n- [ ] Steps to reproduce are exact commands, not descriptions\n- [ ] PoC is a single copy-pasteable command\n- [ ] Baseline\u002Fnegative response is included (proves the PoC is meaningful)\n- [ ] Impact describes only demonstrated effects\n- [ ] Remediation is a specific code fix, not generic advice\n- [ ] Affected version is exact (not \"all versions\" unless verified)\n- [ ] Total report is under 500 words (excluding code blocks)\n- [ ] No filler phrases: \"an attacker could potentially\", \"this might allow\",\n      \"it is recommended to\", \"in certain conditions\"\n- [ ] No severity inflation beyond what the PoC proves\n- [ ] Finding is in scope for the target program\n- [ ] Not a duplicate of an existing finding (`kg_query(kind=\"finding\")`)\n\n## Platform-Specific Notes\n\n### HackerOne\n- Use their severity rating (maps from CVSS)\n- Reference CWE numbers in the weakness field\n- Attach PoC scripts as files if longer than 10 lines\n- Include the CVSS calculator link: `https:\u002F\u002Fwww.first.org\u002Fcvss\u002Fcalculator\u002F3.1#CVSS:3.1\u002F...`\n\n### Bugcrowd\n- Map to their Vulnerability Rating Taxonomy (VRT)\n- P1 = Critical (9.0-10.0), P2 = High (7.0-8.9), P3 = Medium (4.0-6.9), P4 = Low (0.1-3.9)\n\n### GitHub Security Advisories\n- Use the GHSA template: affected package, affected versions, patched versions\n- Include the CWE in the advisory metadata\n- Credit field: your username or team name\n\n### Immunefi\n- Web3\u002FDeFi focus: quantify financial impact when possible\n- Include affected contract addresses if applicable\n- Reference the specific bounty program's scope document\n",{"name":5,"metadata":24,"description":7},{"subdomain":25,"when_to_use":26,"upstream_ref":27},"reporting","bug bounty report hackerone h1 bugcrowd immunefi github security advisory ghsa submission triage cvss writeup","HackerOne \u002F Bugcrowd \u002F Immunefi \u002F GitHub Security Advisory submission templates","main","d6bfd87ad9f910cfff715da04c804638990a8538","packages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fplugins\u002Fverifier\u002Fbounty-report",1,"https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto","2026-10-12 03:35:17",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add a18268941610-crypto\u002FDecepticon-shentou --skill bounty-report-formatter",{"tool":41,"command":42},"bunx","bunx skills add a18268941610-crypto\u002FDecepticon-shentou --skill bounty-report-formatter",{"tool":44,"command":45},"pnpm","pnpm dlx skills add a18268941610-crypto\u002FDecepticon-shentou --skill bounty-report-formatter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fplugins\u002Fverifier\u002Fbounty-report\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7EJXTEFYQPHY32431RWJENT","wps-pixie-dust","WPS Pixie-Dust offline nonce attack (reaver -K \u002F pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7EJXHKBXYF3QSYNW5YSK10H","wpa3-sae","WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7EJXAC5W1C1MACKKP1RRT8K","wpa2-psk","WPA\u002FWPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer\u002FSMB encryption mode in 2026.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7EJX02A5FFBM2V7VG52GNSK","wpa-enterprise-eap","WPA\u002FWPA2\u002FWPA3-Enterprise (802.1X\u002FEAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7EJWNRRMBRZQTKH3VFYAK58","krack-fragattacks","KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation\u002Faggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7EJWB0CC58R8Z4HW6YRQCZW","evil-twin-karma","Evil-twin rogue AP with KARMA\u002FMana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK\u002Fopen networks. Distinct from wpa-enterprise-eap which targets 802.1X.","https:\u002F\u002Fgithub.com\u002Fa18268941610-crypto\u002FDecepticon-shentou\u002Fblob\u002Fmain\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]