[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMDFRCYEXS8XBCHWGJ40QK":3,"skill-same:01M7EMDFRCYEXS8XBCHWGJ40QK":91},{"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":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M7EMDFRCYEXS8XBCHWGJ40QK","implementing-fuzz-testing-in-cicd-with-aflplusplus",null,"Integrates AFL++ coverage-guided fuzzing into CI\u002FCD pipelines, covering harness construction, AFL++\u002FAddressSanitizer\u002FCmpLog instrumentation builds, and persistent-mode fuzzing to discover memory-corruption and input-handling vulnerabilities in C\u002FC++ code. Use when adding automated fuzz testing to a build pipeline or hunting for memory-safety bugs in native\u002Fcompiled applications.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-fuzz-testing-in-cicd-with-aflplusplus\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-fuzz-testing-in-cicd-with-aflplusplus\ndescription: Integrates AFL++ coverage-guided fuzzing into CI\u002FCD pipelines, covering harness construction, AFL++\u002FAddressSanitizer\u002FCmpLog instrumentation builds, and persistent-mode fuzzing to discover memory-corruption and input-handling vulnerabilities in C\u002FC++ code. Use when adding automated fuzz testing to a build pipeline or hunting for memory-safety bugs in native\u002Fcompiled applications.\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- aflplusplus\n- fuzz-testing\n- cicd\n- coverage-guided-fuzzing\n- security-testing\n- vulnerability-discovery\n- afl\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_ai_rmf:\n- MEASURE-2.7\n- MAP-5.1\n- MANAGE-2.4\natlas_techniques:\n- AML.T0070\n- AML.T0066\n- AML.T0082\nnist_csf:\n- PR.PS-01\n- GV.SC-07\n- ID.IM-04\n- PR.PS-04\nmitre_attack:\n- T1195\n- T1554\n- T1059.004\n- T1005\n- T1059\n---\n\n# Implementing Fuzz Testing in CI\u002FCD with AFL++\n\n## Overview\n\nAFL++ (American Fuzzy Lop Plus Plus) is a community-maintained fork of AFL that provides state-of-the-art coverage-guided fuzz testing for discovering vulnerabilities in compiled applications. AFL++ uses genetic algorithms to mutate inputs, tracking code coverage to find new execution paths that trigger crashes, hangs, and undefined behavior. In CI\u002FCD environments, AFL++ can be integrated to continuously test parsers, protocol handlers, file format processors, and any code that handles untrusted input. AFL++ supports persistent mode for high-speed fuzzing (up to 100,000+ executions per second), custom mutators, QEMU mode for binary-only fuzzing, and CmpLog\u002FRedQueen for automatic dictionary extraction.\n\n\n## When to Use\n\n- When deploying or configuring implementing fuzz testing in cicd with aflplusplus capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Linux-based CI runners (AFL++ does not support Windows natively)\n- GCC or Clang compiler toolchain\n- AFL++ installed (`apt install aflplusplus` or built from source)\n- Target application with harness functions isolating input processing\n- Seed corpus of valid input samples\n\n## Core Concepts\n\n### Coverage-Guided Fuzzing\n\nAFL++ instruments the target binary at compile time (or via QEMU\u002FFrida for binary-only targets) to track which code paths each input exercises. When a mutated input triggers a new code path, it is saved to the corpus for further mutation. This feedback loop enables AFL++ to systematically explore program state space.\n\n### Instrumentation Modes\n\n| Mode | Use Case | Performance |\n|------|----------|-------------|\n| `afl-clang-fast` (LTO) | Source available, best performance | Highest |\n| `afl-clang-fast` | Source available, standard | High |\n| `afl-gcc-fast` | GCC-based projects | High |\n| `QEMU mode` | Binary-only, no source | Medium |\n| `Frida mode` | Binary-only, cross-platform | Medium |\n| `Unicorn mode` | Firmware, embedded | Low |\n\n### Persistent Mode\n\nPersistent mode avoids fork overhead by fuzzing within a loop:\n\n```c\n#include \u003Cunistd.h>\n\n__AFL_FUZZ_INIT();\n\nint main() {\n    __AFL_INIT();\n    unsigned char *buf = __AFL_FUZZ_TESTCASE_BUF;\n\n    while (__AFL_LOOP(10000)) {\n        int len = __AFL_FUZZ_TESTCASE_LEN;\n        \u002F\u002F Process buf[0..len-1]\n        parse_input(buf, len);\n    }\n    return 0;\n}\n```\n\n## Workflow\n\n### Step 1 --- Build the Fuzzing Harness\n\nCreate a harness that feeds AFL++ input to the target function:\n\n```c\n\u002F\u002F fuzz_harness.c\n#include \u003Cstdio.h>\n#include \u003Cstdlib.h>\n#include \u003Cstring.h>\n#include \"target_parser.h\"\n\n__AFL_FUZZ_INIT();\n\nint main() {\n    __AFL_INIT();\n    unsigned char *buf = __AFL_FUZZ_TESTCASE_BUF;\n\n    while (__AFL_LOOP(10000)) {\n        int len = __AFL_FUZZ_TESTCASE_LEN;\n        if (len \u003C 4) continue;\n\n        \u002F\u002F Reset state between iterations\n        parser_context_t ctx;\n        parser_init(&ctx);\n        parser_process(&ctx, buf, len);\n        parser_cleanup(&ctx);\n    }\n    return 0;\n}\n```\n\n### Step 2 --- Compile with AFL++ Instrumentation\n\n```bash\n# Standard instrumentation\nexport CC=afl-clang-fast\nexport CXX=afl-clang-fast++\n\n# Enable AddressSanitizer for better crash detection\nexport AFL_USE_ASAN=1\n\n# Build the target with instrumentation\n$CC -o fuzz_harness fuzz_harness.c -ltarget_parser -fsanitize=address\n\n# Build a CmpLog binary for better coverage\n$CC -o fuzz_harness_cmplog fuzz_harness.c -ltarget_parser \\\n  -fsanitize=address -DCMPLOG\n```\n\n### Step 3 --- Prepare Seed Corpus\n\n```bash\nmkdir -p corpus\u002F\n# Add valid input samples\ncp test_inputs\u002F* corpus\u002F\n# Minimize the corpus\nafl-cmin -i corpus\u002F -o corpus_min\u002F -- .\u002Ffuzz_harness @@\n# Further minimize individual inputs\nmkdir -p corpus_tmin\u002F\nfor f in corpus_min\u002F*; do\n    afl-tmin -i \"$f\" -o \"corpus_tmin\u002F$(basename $f)\" -- .\u002Ffuzz_harness @@\ndone\n```\n\n### Step 4 --- Configure CI\u002FCD Integration\n\n**GitHub Actions:**\n\n```yaml\nname: Fuzz Testing\non:\n  push:\n    branches: [main]\n  schedule:\n    - cron: '0 2 * * *'  # Nightly fuzzing\n\njobs:\n  fuzz:\n    runs-on: ubuntu-latest\n    timeout-minutes: 120\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Install AFL++\n        run: |\n          sudo apt-get update\n          sudo apt-get install -y aflplusplus\n\n      - name: Restore corpus cache\n        uses: actions\u002Fcache@v4\n        with:\n          path: corpus\u002F\n          key: fuzz-corpus-${{ github.sha }}\n          restore-keys: fuzz-corpus-\n\n      - name: Build fuzzing harness\n        run: |\n          export CC=afl-clang-fast\n          export AFL_USE_ASAN=1\n          make fuzz_harness\n\n      - name: Run AFL++ fuzzing (CI mode)\n        env:\n          AFL_CMPLOG_ONLY_NEW: 1\n          AFL_FAST_CAL: 1\n          AFL_NO_STARTUP_CALIBRATION: 1\n        run: |\n          mkdir -p findings\u002F\n          timeout 7200 afl-fuzz \\\n            -S ci_fuzzer \\\n            -i corpus\u002F \\\n            -o findings\u002F \\\n            -t 5000 \\\n            -- .\u002Ffuzz_harness @@ || true\n\n      - name: Check for crashes\n        run: |\n          CRASHES=$(find findings\u002F -path \"*\u002Fcrashes\u002F*\" -not -name \"README.txt\" | wc -l)\n          echo \"Found $CRASHES unique crashes\"\n          if [ \"$CRASHES\" -gt 0 ]; then\n            echo \"::error::AFL++ found $CRASHES crashes\"\n            for crash in findings\u002F*\u002Fcrashes\u002F*; do\n              [ -f \"$crash\" ] && echo \"Crash: $crash ($(wc -c \u003C $crash) bytes)\"\n            done\n            exit 1\n          fi\n\n      - name: Update corpus cache\n        if: always()\n        run: |\n          afl-cmin -i findings\u002Fci_fuzzer\u002Fqueue\u002F -o corpus\u002F -- .\u002Ffuzz_harness @@\n```\n\n### Step 5 --- Parallel Fuzzing for Nightly Runs\n\n```bash\n# Launch multiple secondary instances for better coverage\nfor i in $(seq 1 $(nproc)); do\n    afl-fuzz -S fuzzer_$i \\\n      -i corpus\u002F \\\n      -o findings\u002F \\\n      -- .\u002Ffuzz_harness @@ &\ndone\n\n# Wait for all fuzzers\nwait\n\n# Merge and minimize corpus\nafl-cmin -i findings\u002F*\u002Fqueue\u002F -o corpus_merged\u002F -- .\u002Ffuzz_harness @@\n```\n\n### Step 6 --- Crash Triage\n\n```bash\n# Reproduce and categorize crashes\nfor crash in findings\u002F*\u002Fcrashes\u002F*; do\n    echo \"=== Testing: $crash ===\"\n    timeout 5 .\u002Ffuzz_harness_asan \"$crash\" 2>&1 | head -20\n    echo \"---\"\ndone\n\n# Deduplicate crashes by stack trace\nafl-collect findings\u002F crashes_deduped\u002F -- .\u002Ffuzz_harness @@\n```\n\n## CI\u002FCD Best Practices for AFL++\n\n| Setting | CI Short Run | Nightly Long Run |\n|---------|-------------|-----------------|\n| Duration | 30-60 min | 4-24 hours |\n| Mode | `-S` (secondary only) | `-S` (no `-M` for CI) |\n| `AFL_CMPLOG_ONLY_NEW` | 1 | 1 |\n| `AFL_FAST_CAL` | 1 | 0 |\n| `AFL_NO_STARTUP_CALIBRATION` | 1 | 0 |\n| Corpus caching | Required | Required |\n| Parallel instances | 1-2 | nproc |\n\n## Monitoring Fuzzing Campaigns\n\n```bash\n# View fuzzing statistics\nafl-whatsup findings\u002F\n\n# Key metrics to track:\n# - Total paths found (code coverage indicator)\n# - Unique crashes \u002F unique hangs\n# - Stability percentage (should be >90%)\n# - Exec speed (execs\u002Fsec)\n# - Cycles done (full corpus cycles completed)\n```\n\n## References\n\n- [AFL++ Documentation](https:\u002F\u002Faflplus.plus\u002Fdocs\u002F)\n- [AFL++ GitHub Repository](https:\u002F\u002Fgithub.com\u002FAFLplusplus\u002FAFLplusplus)\n- [AFL++ Fuzzing in Depth Guide](https:\u002F\u002Faflplus.plus\u002Fdocs\u002Ffuzzing_in_depth\u002F)\n- [Google Testing Handbook - AFL++](https:\u002F\u002Fappsec.guide\u002Fdocs\u002Ffuzzing\u002Fc-cpp\u002Faflpp\u002F)\n- [OWASP Fuzzing Guide](https:\u002F\u002Fowasp.org\u002Fwww-community\u002FFuzzing)\n","# Implementing Fuzz Testing in CI\u002FCD with AFL++\n\n## Overview\n\nAFL++ (American Fuzzy Lop Plus Plus) is a community-maintained fork of AFL that provides state-of-the-art coverage-guided fuzz testing for discovering vulnerabilities in compiled applications. AFL++ uses genetic algorithms to mutate inputs, tracking code coverage to find new execution paths that trigger crashes, hangs, and undefined behavior. In CI\u002FCD environments, AFL++ can be integrated to continuously test parsers, protocol handlers, file format processors, and any code that handles untrusted input. AFL++ supports persistent mode for high-speed fuzzing (up to 100,000+ executions per second), custom mutators, QEMU mode for binary-only fuzzing, and CmpLog\u002FRedQueen for automatic dictionary extraction.\n\n\n## When to Use\n\n- When deploying or configuring implementing fuzz testing in cicd with aflplusplus capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Linux-based CI runners (AFL++ does not support Windows natively)\n- GCC or Clang compiler toolchain\n- AFL++ installed (`apt install aflplusplus` or built from source)\n- Target application with harness functions isolating input processing\n- Seed corpus of valid input samples\n\n## Core Concepts\n\n### Coverage-Guided Fuzzing\n\nAFL++ instruments the target binary at compile time (or via QEMU\u002FFrida for binary-only targets) to track which code paths each input exercises. When a mutated input triggers a new code path, it is saved to the corpus for further mutation. This feedback loop enables AFL++ to systematically explore program state space.\n\n### Instrumentation Modes\n\n| Mode | Use Case | Performance |\n|------|----------|-------------|\n| `afl-clang-fast` (LTO) | Source available, best performance | Highest |\n| `afl-clang-fast` | Source available, standard | High |\n| `afl-gcc-fast` | GCC-based projects | High |\n| `QEMU mode` | Binary-only, no source | Medium |\n| `Frida mode` | Binary-only, cross-platform | Medium |\n| `Unicorn mode` | Firmware, embedded | Low |\n\n### Persistent Mode\n\nPersistent mode avoids fork overhead by fuzzing within a loop:\n\n```c\n#include \u003Cunistd.h>\n\n__AFL_FUZZ_INIT();\n\nint main() {\n    __AFL_INIT();\n    unsigned char *buf = __AFL_FUZZ_TESTCASE_BUF;\n\n    while (__AFL_LOOP(10000)) {\n        int len = __AFL_FUZZ_TESTCASE_LEN;\n        \u002F\u002F Process buf[0..len-1]\n        parse_input(buf, len);\n    }\n    return 0;\n}\n```\n\n## Workflow\n\n### Step 1 --- Build the Fuzzing Harness\n\nCreate a harness that feeds AFL++ input to the target function:\n\n```c\n\u002F\u002F fuzz_harness.c\n#include \u003Cstdio.h>\n#include \u003Cstdlib.h>\n#include \u003Cstring.h>\n#include \"target_parser.h\"\n\n__AFL_FUZZ_INIT();\n\nint main() {\n    __AFL_INIT();\n    unsigned char *buf = __AFL_FUZZ_TESTCASE_BUF;\n\n    while (__AFL_LOOP(10000)) {\n        int len = __AFL_FUZZ_TESTCASE_LEN;\n        if (len \u003C 4) continue;\n\n        \u002F\u002F Reset state between iterations\n        parser_context_t ctx;\n        parser_init(&ctx);\n        parser_process(&ctx, buf, len);\n        parser_cleanup(&ctx);\n    }\n    return 0;\n}\n```\n\n### Step 2 --- Compile with AFL++ Instrumentation\n\n```bash\n# Standard instrumentation\nexport CC=afl-clang-fast\nexport CXX=afl-clang-fast++\n\n# Enable AddressSanitizer for better crash detection\nexport AFL_USE_ASAN=1\n\n# Build the target with instrumentation\n$CC -o fuzz_harness fuzz_harness.c -ltarget_parser -fsanitize=address\n\n# Build a CmpLog binary for better coverage\n$CC -o fuzz_harness_cmplog fuzz_harness.c -ltarget_parser \\\n  -fsanitize=address -DCMPLOG\n```\n\n### Step 3 --- Prepare Seed Corpus\n\n```bash\nmkdir -p corpus\u002F\n# Add valid input samples\ncp test_inputs\u002F* corpus\u002F\n# Minimize the corpus\nafl-cmin -i corpus\u002F -o corpus_min\u002F -- .\u002Ffuzz_harness @@\n# Further minimize individual inputs\nmkdir -p corpus_tmin\u002F\nfor f in corpus_min\u002F*; do\n    afl-tmin -i \"$f\" -o \"corpus_tmin\u002F$(basename $f)\" -- .\u002Ffuzz_harness @@\ndone\n```\n\n### Step 4 --- Configure CI\u002FCD Integration\n\n**GitHub Actions:**\n\n```yaml\nname: Fuzz Testing\non:\n  push:\n    branches: [main]\n  schedule:\n    - cron: '0 2 * * *'  # Nightly fuzzing\n\njobs:\n  fuzz:\n    runs-on: ubuntu-latest\n    timeout-minutes: 120\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: Install AFL++\n        run: |\n          sudo apt-get update\n          sudo apt-get install -y aflplusplus\n\n      - name: Restore corpus cache\n        uses: actions\u002Fcache@v4\n        with:\n          path: corpus\u002F\n          key: fuzz-corpus-${{ github.sha }}\n          restore-keys: fuzz-corpus-\n\n      - name: Build fuzzing harness\n        run: |\n          export CC=afl-clang-fast\n          export AFL_USE_ASAN=1\n          make fuzz_harness\n\n      - name: Run AFL++ fuzzing (CI mode)\n        env:\n          AFL_CMPLOG_ONLY_NEW: 1\n          AFL_FAST_CAL: 1\n          AFL_NO_STARTUP_CALIBRATION: 1\n        run: |\n          mkdir -p findings\u002F\n          timeout 7200 afl-fuzz \\\n            -S ci_fuzzer \\\n            -i corpus\u002F \\\n            -o findings\u002F \\\n            -t 5000 \\\n            -- .\u002Ffuzz_harness @@ || true\n\n      - name: Check for crashes\n        run: |\n          CRASHES=$(find findings\u002F -path \"*\u002Fcrashes\u002F*\" -not -name \"README.txt\" | wc -l)\n          echo \"Found $CRASHES unique crashes\"\n          if [ \"$CRASHES\" -gt 0 ]; then\n            echo \"::error::AFL++ found $CRASHES crashes\"\n            for crash in findings\u002F*\u002Fcrashes\u002F*; do\n              [ -f \"$crash\" ] && echo \"Crash: $crash ($(wc -c \u003C $crash) bytes)\"\n            done\n            exit 1\n          fi\n\n      - name: Update corpus cache\n        if: always()\n        run: |\n          afl-cmin -i findings\u002Fci_fuzzer\u002Fqueue\u002F -o corpus\u002F -- .\u002Ffuzz_harness @@\n```\n\n### Step 5 --- Parallel Fuzzing for Nightly Runs\n\n```bash\n# Launch multiple secondary instances for better coverage\nfor i in $(seq 1 $(nproc)); do\n    afl-fuzz -S fuzzer_$i \\\n      -i corpus\u002F \\\n      -o findings\u002F \\\n      -- .\u002Ffuzz_harness @@ &\ndone\n\n# Wait for all fuzzers\nwait\n\n# Merge and minimize corpus\nafl-cmin -i findings\u002F*\u002Fqueue\u002F -o corpus_merged\u002F -- .\u002Ffuzz_harness @@\n```\n\n### Step 6 --- Crash Triage\n\n```bash\n# Reproduce and categorize crashes\nfor crash in findings\u002F*\u002Fcrashes\u002F*; do\n    echo \"=== Testing: $crash ===\"\n    timeout 5 .\u002Ffuzz_harness_asan \"$crash\" 2>&1 | head -20\n    echo \"---\"\ndone\n\n# Deduplicate crashes by stack trace\nafl-collect findings\u002F crashes_deduped\u002F -- .\u002Ffuzz_harness @@\n```\n\n## CI\u002FCD Best Practices for AFL++\n\n| Setting | CI Short Run | Nightly Long Run |\n|---------|-------------|-----------------|\n| Duration | 30-60 min | 4-24 hours |\n| Mode | `-S` (secondary only) | `-S` (no `-M` for CI) |\n| `AFL_CMPLOG_ONLY_NEW` | 1 | 1 |\n| `AFL_FAST_CAL` | 1 | 0 |\n| `AFL_NO_STARTUP_CALIBRATION` | 1 | 0 |\n| Corpus caching | Required | Required |\n| Parallel instances | 1-2 | nproc |\n\n## Monitoring Fuzzing Campaigns\n\n```bash\n# View fuzzing statistics\nafl-whatsup findings\u002F\n\n# Key metrics to track:\n# - Total paths found (code coverage indicator)\n# - Unique crashes \u002F unique hangs\n# - Stability percentage (should be >90%)\n# - Exec speed (execs\u002Fsec)\n# - Cycles done (full corpus cycles completed)\n```\n\n## References\n\n- [AFL++ Documentation](https:\u002F\u002Faflplus.plus\u002Fdocs\u002F)\n- [AFL++ GitHub Repository](https:\u002F\u002Fgithub.com\u002FAFLplusplus\u002FAFLplusplus)\n- [AFL++ Fuzzing in Depth Guide](https:\u002F\u002Faflplus.plus\u002Fdocs\u002Ffuzzing_in_depth\u002F)\n- [Google Testing Handbook - AFL++](https:\u002F\u002Fappsec.guide\u002Fdocs\u002Ffuzzing\u002Fc-cpp\u002Faflpp\u002F)\n- [OWASP Fuzzing Guide](https:\u002F\u002Fowasp.org\u002Fwww-community\u002FFuzzing)\n",{"name":5,"tags":24,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":40,"description":7,"nist_ai_rmf":41,"mitre_attack":45,"atlas_techniques":51},[25,26,27,28,29,30,31],"aflplusplus","fuzz-testing","cicd","coverage-guided-fuzzing","security-testing","vulnerability-discovery","afl","mahipal","cybersecurity","1.0",[36,37,38,39],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04","devsecops",[42,43,44],"MEASURE-2.7","MAP-5.1","MANAGE-2.4",[46,47,48,49,50],"T1195","T1554","T1059.004","T1005","T1059",[52,53,54],"AML.T0070","AML.T0066","AML.T0082","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fimplementing-fuzz-testing-in-cicd-with-aflplusplus",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-fuzz-testing-in-cicd-with-aflplusplus",{"tool":69,"command":70},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-fuzz-testing-in-cicd-with-aflplusplus",{"tool":72,"command":73},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-fuzz-testing-in-cicd-with-aflplusplus","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-fuzz-testing-in-cicd-with-aflplusplus\u002FSKILL.md",true,[77,83,87],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fapi-reference.md","REFERENCE","参考文档",2114,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-fuzz-testing-in-cicd-with-aflplusplus\u002Freferences\u002Fapi-reference.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fstandards.md",1800,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-fuzz-testing-in-cicd-with-aflplusplus\u002Freferences\u002Fstandards.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fworkflows.md",1416,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-fuzz-testing-in-cicd-with-aflplusplus\u002Freferences\u002Fworkflows.md",[92,101,106,113,120,127],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":102,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":100},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":100},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":100},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":100},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":100},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]